From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, master, updated. release_1-9-11-73-gedb3cfc
Date: Wed, 16 Jun 2010 00:35:16 +0200 [thread overview]
Message-ID: <87eig7j55n.fsf@gnu.org> (raw)
In-Reply-To: 877hm0rl56.fsf@ambire.localdomain
Hi!
Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> The ‘--ttn’ can also be omitted since we’d rather communicate by email
> than via comments in ‘configure.ac’. :-)
>
> That's a personal style point, i'd say. Do you really insist on its removal?
More importantly, I insist on reaching a consensus. :-)
There are places in the old C code base where people really seemed to be
talking to each other via comments. That seems misplaced to me.
Development discussions should take place on this mailing list IMO.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-06-15 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1OOUGG-0001JC-VC@vcs-noshell.in.savannah.gnu.org>
2010-06-15 21:08 ` [Guile-commits] GNU Guile branch, master, updated. release_1-9-11-73-gedb3cfc Ludovic Courtès
2010-06-15 22:22 ` Thien-Thi Nguyen
2010-06-15 22:35 ` Ludovic Courtès [this message]
2010-06-16 7:25 ` Andy Wingo
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=87eig7j55n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.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).