From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script
Date: Tue, 2 Aug 2005 21:30:42 -0400 [thread overview]
Message-ID: <20050803013042.GF5762@mythryan2.michonline.com> (raw)
In-Reply-To: <7vbr4jmhqe.fsf@assigned-by-dhcp.cox.net>
On Sun, Jul 31, 2005 at 02:45:29AM -0700, Junio C Hamano wrote:
> Ryan Anderson <ryan@michonline.com> writes:
>
> > All emails are sent as a reply to the previous email, making it easy to
> > skip a collection of emails that are uninteresting.
>
> I understand why _some_ people consider this preferable, but
> wonder if this should have a knob to be tweaked.
>
> For example, I myself often find it very hard to read when
> a cascading thread goes very deep like this:
>
> [PATCH 0/9] cover
> [PATCH 1/9] first one
> [PATCH 2/9] second one
> [PATCH 3/9] third one in the series
> ...
>
> and prefer to see this instead (this assumes your MUA is
> half-way decent and lets you sort by subject):
>
> [PATCH 0/9] cover
> [PATCH 1/9] first one
> [PATCH 2/9] second one
> [PATCH 3/9] third one in the series
> ...
In testing this, I think I figured out *why* the former is preferred -
it guarantees the sorting when in the standard mode of "order by date".
Since these emails are sent *very* fast, delivery order tends to be the
dominating factor in how they sort in your inbox, as they will all have
the same time. So that's a trifle annoying.
Yes, sorting by subject will fix it, but "threaded + subject" is
actually something I'm not sure much of anything supports. (It's not
instantly obvious how to do it in mutt, for example - though,
admittedly, Mutt may very well have a way to do it.)
I noticed this while testing my 2 new fixes - those will sent in a few
seconds.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-08-03 1:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 8:17 [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31 8:17 ` [PATCH 2/3] Add documentation for git-send-email-script Ryan Anderson
2005-07-31 8:17 ` [PATCH 3/3] Add new dependencies caused by git-send-email-script to debian/control Ryan Anderson
2005-07-31 8:24 ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31 9:36 ` Matthias Urlichs
2005-07-31 9:45 ` Junio C Hamano
2005-07-31 19:13 ` Junio C Hamano
2005-07-31 23:52 ` Ryan Anderson
2005-08-01 0:40 ` Junio C Hamano
2005-08-01 7:59 ` Matthias Urlichs
[not found] ` <20050801220800.GA12331@uglybox.localnet>
[not found] ` <20050801224308.GB12331@uglybox.localnet>
[not found] ` <7vk6j52qhn.fsf_-_@assigned-by-dhcp.cox.net>
2005-08-02 12:48 ` [OT] Perl-ish perl vs. C-ish perl Noel Maddy
2005-08-02 16:37 ` Junio C Hamano
2005-08-02 17:20 ` Noel Maddy
2005-08-03 1:30 ` Ryan Anderson [this message]
2005-08-03 7:32 ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Matthias Urlichs
2005-07-31 10:25 ` Johannes Schindelin
2005-07-31 23:54 ` Ryan Anderson
2005-07-31 10:50 ` Sergey Vlasov
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=20050803013042.GF5762@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).