Re: [PATCH] git-format-patch: Make the second and subsequent mails replies to the first

From: Jakub Narebski <jnareb@gmail.com>
Date: Jul 10, 2006, 20:25 UTC
Message-ID: <e8ud22$jo1$1@sea.gmane.org>
In-Reply-To: <1152549787.8890.36.camel@josh-work.beaverton.ibm.com>

Josh Triplett wrote:

Show 12 quoted lines

> On Mon, 2006-07-10 at 18:29 +0200, Erik Mouw wrote:
>> On Mon, Jul 10, 2006 at 06:01:48PM +0200, Johannes Schindelin wrote:
>> > please make that behaviour optional.
>> 
>> Rather make it consistent with git-send-email. Principle of least
>> surprise.
> 
> Well, git-send-email does not include an option to disable the threading
> headers, so consistency with git-send-email would imply not including
> any such option.  I can, however, implement a --no-thread option to omit
> the headers, as well as git-send-email's --in-reply-to option to set an
> initial In-Reply-To/References.  New patch series shortly.

git-send-email has three ways of sending files:
 1. Chain Reply-To:, where every patch refers to earlier in series.
    Ugly in threaded mail/news readers, harder to comment, but there is
    no way to loose the order (e.g. if patches are not numbered *blush*)
 2. No chain reply-to, with cover letter introducing patch series.
    IMHO nicest format... provided there are no errors nor mistakes.
 3. No chain reply-to, without cover letter. I presonally don't like 
    this format, YMMV.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git