From: Peter Zijlstra <peterz@infradead.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Ingo Oeser <ioe-lkml@rameria.de>,
Junio C Hamano <gitster@pobox.com>,
L-K <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: git-send-email
Date: Thu, 12 Feb 2009 23:17:05 +0100 [thread overview]
Message-ID: <1234477025.10603.38.camel@laptop> (raw)
In-Reply-To: <20090212192104.GD15809@csclub.uwaterloo.ca>
On Thu, 2009-02-12 at 14:21 -0500, Lennart Sorensen wrote:
> On Thu, Feb 12, 2009 at 06:25:34PM +0100, Ingo Oeser wrote:
> > No, they are great, if you like to skip over a topic, you are not
> > interested in at all!
> >
> > If you don't like it, just switch off thread in your mailer and
> > don't force this on everybody else!
>
> Actually if (as apparently many people seem to manage to do) you have a
> single starting email, with all the patches as replies to that first
> email, it looks a lot better, and is much easier to follow.
>
> Seperate threads would be bad.
>
> foobar patch 0 (usually a summary/overview)
> +-foobar patch 1
> +-foobar patch 2
> +-foobar patch 3
> +-foobar patch 4
> +-foobar patch 5
>
> is much nicer than
>
> foobar patch 0
> +-foobar patch 1
> +-foobar patch 2
> +-foobar patch 3
> +-foobar patch 4
> +-foobar patch 5
>
> which seems to be what git does itself.
Which happens to be exactly what my suggestion would accomplish.
--[no-]chain-reply-to
If this is set, each email will be sent as a reply to the
previous email sent. If disabled with "--no-chain-reply-to", all
emails after the first will be sent as replies to the first
email sent. When using this, it is recommended that the first
file given be an overview of the entire patch series. Default is
the value of the sendemail.chainreplyto configuration value; if
that is unspecified, default to --chain-reply-to.
next prev parent reply other threads:[~2009-02-12 22:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 15:15 git-send-email Peter Zijlstra
2009-02-12 17:25 ` git-send-email Ingo Oeser
2009-02-12 17:27 ` git-send-email Peter Zijlstra
2009-02-12 19:21 ` git-send-email Lennart Sorensen
2009-02-12 22:17 ` Peter Zijlstra [this message]
2009-02-13 9:34 ` git-send-email Ingo Oeser
2009-02-13 16:39 ` git-send-email Lennart Sorensen
2009-02-13 22:25 ` git-send-email Junio C Hamano
2009-02-15 17:20 ` git-send-email Stefan Richter
2009-02-15 18:30 ` git-send-email Peter Zijlstra
2009-02-15 19:25 ` git-send-email Stefan Richter
2009-02-16 20:58 ` git-send-email Joel Becker
2009-02-13 2:16 ` git-send-email Junio C Hamano
2009-02-13 9:22 ` git-send-email Peter Zijlstra
2009-02-13 9:27 ` git-send-email Willy Tarreau
2009-02-13 18:13 ` git-send-email H. Peter Anvin
2009-02-13 18:59 ` git-send-email Cyrill Gorcunov
2009-02-16 23:51 ` git-send-email Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 21:13 git-send-email Uwe Kleine-König
2007-02-22 21:38 ` git-send-email Junio C Hamano
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=1234477025.10603.38.camel@laptop \
--to=peterz@infradead.org \
--cc=gitster@pobox.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.