From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <junkio@cox.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Andy Parkins <andyparkins@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] qgit4: Add a header and set the font family appropriately to the log message
Date: Thu, 8 Feb 2007 16:29:17 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702081623460.8424@woody.linux-foundation.org> (raw)
In-Reply-To: <7vk5ysw6a3.fsf@assigned-by-dhcp.cox.net>
On Thu, 8 Feb 2007, Junio C Hamano wrote:
>
> This came up before, but when you have more than 9 in your
> series, we _could_ do [PATCH 01/12] ... [PATCH 12/12] to line
> them up in e-mail client of the recipients better.
Not just "line them up". It's more than just a visual thing.
So I long ago I asked Andrew to do that for me in his scripts, because
when he sends me 150+ patches in one go, and I want to sort them to be in
order, I can't depend on arrival order (because it won't be reliable) and
I can't necessarily depend on date order (because he can send more than
one patch a second), so what do I do? I sort by subject.
But I don't know of a _single_ email reader (and certainly not the one I
use) that can "sort numerically by subject, using field #2". So it's a lot
easier if the numbering is sorted _alphabetically_ rather than
numerically.
Otherwise I tend to see things like
[PATCH 1/89]
[PATCH 10/89]
[PATCH 11/89]
...
[PATCH 2/89]
[PATCH 20/89]
[PATCH 21/89]
...
(note that this was mostly a problem just when syncing with Andrew: if the
patch series is just in the teens or something, it may not sort easily,
but you can just pick out the individual emails in order. When you have
hundreds of patches, suddenly you realize that computers sorting them for
you is really convenient).
Linus
next prev parent reply other threads:[~2007-02-09 0:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 21:38 [PATCH] qgit: Default the log window to wider than the file list and set monospaced font Andy Parkins
2007-02-08 8:39 ` Marco Costalba
2007-02-08 9:46 ` Jakub Narebski
2007-02-08 10:20 ` Andy Parkins
2007-02-08 19:06 ` Marco Costalba
2007-02-08 19:12 ` Andy Parkins
2007-02-08 19:29 ` Marco Costalba
2007-02-08 19:51 ` Marco Costalba
2007-02-08 21:58 ` Andy Parkins
2007-02-08 23:31 ` [PATCH] qgit4: Add a header and set the font family appropriately to the log message Andy Parkins
2007-02-08 23:41 ` Shawn O. Pearce
2007-02-08 23:58 ` Junio C Hamano
2007-02-09 0:29 ` Linus Torvalds [this message]
2007-02-09 0:43 ` [PATCH] format-patch -n: make sorting easier by padding number Johannes Schindelin
2007-02-09 0:47 ` Johannes Schindelin
2007-02-09 9:19 ` [PATCH] qgit4: Add a header and set the font family appropriately to the log message Michael S. Tsirkin
2007-02-09 5:44 ` Marco Costalba
2007-02-08 23:31 ` [PATCH] qgit4: Removed the monospace font override from the log viewer box Andy Parkins
2007-02-08 23:31 ` [PATCH] qgit4: Set a 5:1 stretch ratio on the left and right halves of the patch viewer Andy Parkins
2007-02-08 23:04 ` [PATCH] qgit: Default the log window to wider than the file list and set monospaced font Andy Parkins
2007-02-08 10:22 ` Andy Parkins
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=Pine.LNX.4.64.0702081623460.8424@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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.