From: Nala Ginrut <nalaginrut@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Cc: baux@member.fsf.org, linas@linas.org
Subject: Is guile-dbi still mainaining?
Date: Thu, 07 Feb 2013 16:11:54 +0800 [thread overview]
Message-ID: <1360224714.12087.8.camel@Renee-desktop.suse> (raw)
Hi Boriani & Vepstas !
I'm dealing with a web-framework and using guile-dbi & guile-dbd, which
are nice thing to handle the databases. ;-)
I found there're something obsoleted in the current code, when I tried
to format a patch I've noticed the bug-report&patches haven't been
responded since 2010.
So I think it's better to ping you here.
I plan to fork it on github and package them for guildhall.
If it's OK for you, please let me know. ;-)
Thanks!
next reply other threads:[~2013-02-07 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 8:11 Nala Ginrut [this message]
2013-02-07 13:16 ` Is guile-dbi still mainaining? Mike Gran
2013-02-07 13:43 ` Nala Ginrut
2013-02-07 15:19 ` Thien-Thi Nguyen
2013-02-07 15:55 ` Nala Ginrut
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=1360224714.12087.8.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--cc=baux@member.fsf.org \
--cc=guile-devel@gnu.org \
--cc=linas@linas.org \
/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).