From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Cleanup mark-during-GC debug checks.
Date: Tue, 09 Sep 2008 20:15:29 +0200 [thread overview]
Message-ID: <m3hc8p6v9a.fsf@pobox.com> (raw)
In-Reply-To: <87sks9i5ow.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 09 Sep 2008 19:34:39 +0200")
On Tue 09 Sep 2008 19:34, ludo@gnu.org (Ludovic Courtès) writes:
> 1. I don't want to use a web interface to review code. Most free
> software projects use email in one form or another, which I find
> convenient. Having patches in-lined is optimal IMO.
Me neither. OTOH a web front-end is also nice. Bundle-buggy seems to be
what I want:
http://code.aaronbentley.com/bundlebuggy/
But we'd have to hack it to do git.
> 2. I don't want to have a Google account.
Me neither.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2008-09-09 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 14:39 Cleanup mark-during-GC debug checks hanwenn
2008-09-09 17:34 ` Ludovic Courtès
2008-09-09 18:15 ` Andy Wingo [this message]
2008-09-10 1:13 ` Han-Wen Nienhuys
2008-09-10 7:36 ` Ludovic Courtès
2008-09-10 19:12 ` 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=m3hc8p6v9a.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).