From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: William Giokas <1007380@gmail.com>, git@vger.kernel.org
Subject: Re: [bug report] git-am applying maildir patches in reverse
Date: Fri, 01 Mar 2013 15:24:42 -0800 [thread overview]
Message-ID: <7vlia6em9x.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130301230508.GC862@sigill.intra.peff.net> (Jeff King's message of "Fri, 1 Mar 2013 18:05:08 -0500")
Jeff King <peff@peff.net> writes:
> On Fri, Mar 01, 2013 at 05:52:31PM -0500, Jeff King wrote:
> ...
>> The maildir spec explicitly says that readers should not make
>> assumptions about the content of the filenames. Mutt happens to write
>> them as:
>>
>> ${epoch_seconds}.${pid}_${seq}.${host}
>>
>> so in practice, sorting them kind of works. Except that ...
>> << it does not work >> ...
> That ordering is not necessarily useful.
> ...
> So it is somewhat against the maildir spec, but I think in practice it
> would help.
I do not think it would help, unless these epoch_seconds are the
sender timestamps. And the number of digits in epoch-seconds for
recent messages would be the same, so ordering textually would be
sufficient if ordering by timestamp were.
next prev parent reply other threads:[~2013-03-01 23:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 22:20 [bug report] git-am applying maildir patches in reverse William Giokas
2013-03-01 22:27 ` Junio C Hamano
2013-03-01 22:52 ` Jeff King
2013-03-01 23:05 ` Jeff King
2013-03-01 23:24 ` Junio C Hamano [this message]
2013-03-01 23:35 ` Jeff King
2013-03-01 23:57 ` Junio C Hamano
2013-03-02 0:38 ` Jeff King
2013-03-02 0:08 ` Junio C Hamano
2013-03-02 0:41 ` Jeff King
2013-03-02 8:44 ` Andreas Schwab
2013-03-03 6:22 ` Junio C Hamano
2013-03-03 6:32 ` Jeff King
2013-03-03 6:26 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vlia6em9x.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=1007380@gmail.com \
--cc=git@vger.kernel.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).