From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: [PATCH] scm_module_variable, duplicate bindings handlers
Date: Mon, 13 Aug 2007 10:08:04 +0100 [thread overview]
Message-ID: <87absv94zv.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <873ayrh250.fsf@chbouib.org> (Ludovic Courtès's message of "Fri, 10 Aug 2007 16:53:31 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> So both patches make sense.
Agreed, but you may also want to write some tests, to check and
document the behaviour that you expect for guile-gnome. Otherwise
there's nothing to catch someone accidentally reverting this change
again.
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2007-08-13 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 9:53 [PATCH] scm_module_variable, duplicate bindings handlers Andy Wingo
2007-08-10 14:53 ` Ludovic Courtès
2007-08-13 9:08 ` Neil Jerram [this message]
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=87absv94zv.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/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).