From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-format-patch: Make the second and subsequent mails replies to the first
Date: Mon, 10 Jul 2006 22:25:08 +0200 [thread overview]
Message-ID: <e8ud22$jo1$1@sea.gmane.org> (raw)
In-Reply-To: 1152549787.8890.36.camel@josh-work.beaverton.ibm.com
Josh Triplett wrote:
> 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
next prev parent reply other threads:[~2006-07-10 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 15:44 [PATCH] git-format-patch: Make the second and subsequent mails replies to the first Josh Triplett
2006-07-10 16:01 ` Johannes Schindelin
2006-07-10 16:29 ` Erik Mouw
2006-07-10 16:43 ` Josh Triplett
2006-07-10 20:25 ` Jakub Narebski [this message]
2006-07-10 18:41 ` [PATCH 1/3] " Josh Triplett
2006-07-10 21:44 ` Junio C Hamano
2006-07-14 17:16 ` Josh Triplett
2006-07-14 18:23 ` Junio C Hamano
2006-07-14 19:20 ` Josh Triplett
2006-07-14 19:32 ` Junio C Hamano
2006-07-15 7:45 ` Petr Baudis
2006-07-15 8:10 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-07-15 0:48 [PATCH] " Josh Triplett
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e8ud22$jo1$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).