From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Ricardo Wurmus <rekado@elephly.net>, tomas@tuxteam.de
Cc: guile-user@gnu.org
Subject: Re: Source of guile-dbi
Date: Wed, 7 Oct 2020 16:14:22 +0200 [thread overview]
Message-ID: <e7a4bbd7-257a-a4e7-1b69-2b0dd82e7be7@posteo.de> (raw)
In-Reply-To: <87r1qbzjj2.fsf@elephly.net>
Hi Ricardo and hi Tomas!
On 10/6/20 1:22 PM, Ricardo Wurmus wrote:
> Hi tomas,
>
>> what is currently the canonical source of guile DBI? Is it
>> the github opencog one [1]? I'm asking because I didn't want
>> to (unnecessarily) go through github.
> this works:
>
> http://web.archive.org/web/20170225155326/http://download.gna.org/guile-dbi/guile-dbi-2.1.6.tar.gz
I this outdated then?
https://notabug.org/ZelphirKaltstahl/awesome-guile/src/master/list.md#databases
Best regards,
Zelphir
next prev parent reply other threads:[~2020-10-07 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 8:29 Source of guile-dbi tomas
2020-10-06 11:22 ` Ricardo Wurmus
2020-10-06 11:23 ` tomas
2020-10-07 14:14 ` Zelphir Kaltstahl [this message]
2020-10-07 14:17 ` tomas
2020-10-07 15:49 ` tomas
2020-10-08 21:15 ` Aleix Conchillo Flaqué
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7a4bbd7-257a-a4e7-1b69-2b0dd82e7be7@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
--cc=rekado@elephly.net \
--cc=tomas@tuxteam.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).