From: Andy Wingo <wingo@pobox.com>
To: hanwen@xs4all.nl
Cc: guile-devel@gnu.org
Subject: Re: Cleanup mark-during-GC debug checks.
Date: Wed, 10 Sep 2008 21:12:52 +0200 [thread overview]
Message-ID: <m3zlmf6ci3.fsf@pobox.com> (raw)
In-Reply-To: <ga771j$6l1$1@ger.gmane.org> (Han-Wen Nienhuys's message of "Tue, 09 Sep 2008 22:13:02 -0300")
On Wed 10 Sep 2008 03:13, Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> My experience is that a web interface (which tracks different versions of
> the same patch) is a lot easier when it is a major change with lots of
> revisions.
I can definitely see the value in this. But to take discussions away
from the list probably isn't the way to go ;)
> In general, I find cutting & pasting patches into emails clumsy and error
> prone. In general, git is much better suited for sending patches around.
Yep, to make a git-request-pull message is easier, can just pipe to a
mailer.
Seriously, git needs bundle buggy! http://bundlebuggy.aaronbentley.com/
Piling on a bikeshed,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2008-09-10 19:12 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
2008-09-10 1:13 ` Han-Wen Nienhuys
2008-09-10 7:36 ` Ludovic Courtès
2008-09-10 19:12 ` Andy Wingo [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=m3zlmf6ci3.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).