From: Andreas Ericsson <ae@op5.se>
To: Jeff King <peff@peff.net>
Cc: david@lang.hm, Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: send-email sending shallow threads by default
Date: Tue, 17 Feb 2009 09:30:40 +0100 [thread overview]
Message-ID: <499A75B0.5050600@op5.se> (raw)
In-Reply-To: <20090216000732.GC3503@coredump.intra.peff.net>
Jeff King wrote:
> On Sun, Feb 15, 2009 at 03:53:50PM -0800, david@lang.hm wrote:
>
>>> * git-send-email won't make deep threads by default
>>>
>>> Many people said that by default when sending more than 2 patches the
>>> threading git-send-email makes by default is hard to read, and they
>>> prefer the default be one cover letter and each patch as a direct
>>> follow-up to the cover letter.
>>>
>>> http://article.gmane.org/gmane.comp.version-control.git/109790
>> I have mixed feelings about this one, if some messages get delayed in
>> transit the deep threads still keeps them in order, while the 2-layer
>> option doesn't.
>
> Is that the case? mutt at least orders by thread, but by rfc822 date
> within a single level of thread. So as long as the date fields (set by
> the sender) are correct, it looks right no matter what order they arrive
> in.
>
> Are there common readers that thread but do not order by date?
>
Thunderbird does it. I haven't found an option to sort by "date sent"
inside threads, .
FWIW, I like this change either way. Deep threading is nice for up to
five or so patches. After that it becomes messy. Shallow threading
simply scales much better, so it's easier to be consistent if that's
the default.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2009-02-17 8:32 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 21:31 [RFC - draft] List of proposed future changes that are backward incompatible Junio C Hamano
2009-02-15 21:48 ` Junio C Hamano
2009-02-15 22:56 ` Jakub Narebski
2009-02-15 23:39 ` Junio C Hamano
2009-02-15 23:20 ` Heikki Orsila
2009-02-16 0:04 ` disallowing push to currently checked-out branch Jeff King
2009-02-16 1:33 ` david
2009-02-16 1:47 ` david
2009-02-16 1:30 ` Julian Phillips
2009-02-16 4:01 ` Jeff King
2009-02-16 8:33 ` Daniel Barkalow
2009-02-16 8:51 ` Junio C Hamano
2009-02-16 10:17 ` Sergio Callegari
2009-02-16 13:58 ` Jeff King
2009-02-16 17:13 ` Sergio Callegari
2009-02-16 17:33 ` Matthieu Moy
2009-02-16 17:43 ` Johannes Schindelin
2009-02-16 18:48 ` Jay Soffian
2009-02-16 20:02 ` Johannes Schindelin
2009-02-16 21:12 ` Jay Soffian
2009-02-16 21:15 ` Johannes Schindelin
2009-02-16 22:28 ` Jay Soffian
2009-02-16 22:52 ` Jeff King
2009-02-17 5:53 ` Jay Soffian
2009-02-17 11:28 ` PUSH_HEAD, was " Johannes Schindelin
2009-02-17 17:29 ` Jay Soffian
2009-02-17 19:48 ` Jeff King
2009-02-17 22:20 ` Junio C Hamano
2009-02-17 22:42 ` Jay Soffian
2009-02-17 22:54 ` Johannes Schindelin
2009-02-16 19:24 ` Sergio Callegari
2009-02-16 20:09 ` Johannes Schindelin
2009-02-16 21:42 ` Jay Soffian
2009-02-17 0:07 ` Sergio Callegari
2009-02-17 0:18 ` Johannes Schindelin
2009-02-17 0:41 ` Sergio Callegari
2009-02-17 0:56 ` Johannes Schindelin
2009-02-17 1:18 ` Junio C Hamano
2009-02-17 0:57 ` Junio C Hamano
2009-02-16 21:43 ` Junio C Hamano
2009-02-16 22:43 ` Jeff King
2009-02-16 23:23 ` Junio C Hamano
2009-02-17 0:23 ` Jeff King
2009-02-17 0:43 ` Junio C Hamano
2009-02-17 1:29 ` Jeff King
2009-02-16 3:50 ` Jeff King
2009-02-16 5:05 ` david
2009-02-16 4:05 ` Jeff King
2009-02-16 5:18 ` david
2009-02-16 4:37 ` Jeff King
2009-02-16 5:55 ` david
2009-02-16 5:06 ` Jeff King
2009-02-16 10:53 ` Johannes Schindelin
2009-02-16 10:50 ` dashed commands, was " Johannes Schindelin
2009-02-15 23:53 ` [RFC - draft] List of proposed future changes that are backward incompatible david
2009-02-15 23:01 ` Johannes Schindelin
2009-02-15 23:36 ` Junio C Hamano
2009-02-16 0:14 ` david
2009-02-15 23:18 ` Johannes Schindelin
2009-02-16 0:38 ` david
2009-02-16 0:29 ` Junio C Hamano
2009-02-16 10:23 ` Johannes Schindelin
2009-02-16 15:33 ` david
2009-02-16 14:40 ` Sverre Rabbelier
2009-02-16 0:02 ` disallowing push to currently checked-out branch Jeff King
2009-02-16 10:06 ` Sergio Callegari
2009-02-15 23:01 ` [RFC - draft] List of proposed future changes that are backward incompatible Jakub Narebski
2009-02-15 23:15 ` Johannes Schindelin
2009-02-15 23:38 ` Jakub Narebski
2009-02-16 0:35 ` david
2009-02-16 0:07 ` send-email sending shallow threads by default Jeff King
2009-02-16 0:09 ` Pieter de Bie
2009-02-16 2:43 ` Jeff King
2009-02-16 2:55 ` Brian Gernhardt
2009-02-16 9:56 ` Wincent Colaiuta
2009-02-16 7:55 ` SZEDER Gábor
2009-02-16 10:38 ` Martin Mares
2009-02-17 8:34 ` Andreas Ericsson
2009-02-17 9:06 ` Martin Mares
2009-02-17 19:28 ` Jeff King
2009-02-20 3:03 ` Eric W. Biederman
2009-02-20 3:26 ` Jeff King
2009-02-20 4:13 ` Eric W. Biederman
2009-02-17 8:30 ` Andreas Ericsson [this message]
2009-02-16 1:27 ` [RFC - draft] List of proposed future changes that are backward incompatible Sitaram Chamarty
2009-02-16 8:04 ` Björn Steinbrink
2009-02-16 8:49 ` Junio C Hamano
2009-02-16 9:07 ` Björn Steinbrink
2009-02-16 2:42 ` [RFC - draft #2] " Junio C Hamano
2009-02-16 3:20 ` Jeff King
2009-02-16 21:10 ` Jakub Narebski
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=499A75B0.5050600@op5.se \
--to=ae@op5.se \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).