From: Willy Tarreau <w@1wt.eu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Junio C Hamano <junio@pobox.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Ingo Oeser <ioe-lkml@rameria.de>,
L-K <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: git-send-email
Date: Fri, 13 Feb 2009 10:27:37 +0100 [thread overview]
Message-ID: <20090213092737.GO5038@1wt.eu> (raw)
In-Reply-To: <1234516958.6519.6.camel@twins>
Hi Peter,
On Fri, Feb 13, 2009 at 10:22:38AM +0100, Peter Zijlstra wrote:
> On Thu, 2009-02-12 at 18:16 -0800, Junio C Hamano wrote:
> > lsorense@csclub.uwaterloo.ca (Lennart Sorensen) writes:
> >
> > > 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.
> >
> > I personally prefer the former, but as you hopefully all found out by now,
> > the choice between these two is just the matter of personal taste, and
> > there is no clear majority.
> >
> > The default will not going to change.
>
> Its a matter of usability, the inf deep chain git does by default
> renders the result unusable. Fact is I usually skip over patch series
> posted that way, simply because its too much of a bother.
>
> If you can't be bothered with usability of your project, then so be it.
> Maybe all those rants on how unusable git is have a point after all.
While your last comment seems a bit excessive to me, I agree with you
about the threading problem. I have to turn threads off to read some
of these long mails because the subject does not fit in my terminal,
and most of the time I only see just something like '[PATCH' which is
pretty useless.
The former mode (as used by Greg when he posts his huge stable series)
is a lot more convenient. Also, if one mail gets dropped for whatever
reason in between, the threading is not broken.
Regards,
Willy
next prev parent reply other threads:[~2009-02-13 9:28 UTC|newest]
Thread overview: 18+ 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 ` git-send-email Peter Zijlstra
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 ` Willy Tarreau [this message]
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
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=20090213092737.GO5038@1wt.eu \
--to=w@1wt.eu \
--cc=ioe-lkml@rameria.de \
--cc=junio@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox