From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: "Fernando J. Pereda" <ferdy@ferdyx.org>, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Teach mailsplit about Maildir's
Date: Sun, 20 May 2007 21:27:17 +0200 [thread overview]
Message-ID: <200705202127.17723.johan@herland.net> (raw)
In-Reply-To: <20070520191821.GF13197@ferdyx.org>
On Sunday 20 May 2007, Fernando J. Pereda wrote:
> On Sun, May 20, 2007 at 08:53:32PM +0200, Johan Herland wrote:
> > I use KMail with Maildir for all my mail, except for my "patches" mail folder
> > where I copy patches to import into my repos (which is in mbox format).
> > KMail makes it easy to mix mbox and Maildir folders, so it's not really a
> > big deal for me, but I would of course prefer Maildir support if it's
> > possible to get it right.
> >
> > Not sure how I feel about the usefulness of the patch if it requires correct
> > sorting, and most mail clients turn out to _not_ sort correctly. Of course
> > I have no idea what most mail clients do, but KMail seems to get it about
> > right, AFAICS (mail filename starts with timestamp, so they're at least
> > sorted roughly on (arrival) date).
>
> [ I sent this only to Johan, re-sending to the rest of the people now.
> Sorry Johan for the dupe ]
>
> I discussed this with a pine user in #git and we concluded (looking at
> the respective code) that both Mutt and Pine generate correct filenames
> based on when that mail arrived to the Maildir.
>
> I use Mutt, and to test it I picked a thread that didn't arrive in
> order, tagged and copied it to a different Maildir, patches were
> splitted in correct order.
Well, if Mutt, Pine, and KMail all get it right, then it looks like a
useful feature to add.
Does anybody now of (current versions of) mail clients that do _not_
get this right?
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2007-05-20 19:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 18:14 [PATCH] Teach mailsplit about Maildir's Fernando J. Pereda
2007-05-20 18:36 ` Junio C Hamano
2007-05-20 18:49 ` Alex Riesen
2007-05-20 19:00 ` Fernando J. Pereda
2007-05-20 20:35 ` Alex Riesen
2007-05-20 20:44 ` Fernando J. Pereda
2007-05-20 18:53 ` Johan Herland
2007-05-20 19:18 ` Fernando J. Pereda
2007-05-20 19:27 ` Johan Herland [this message]
2007-05-21 12:55 ` Johannes Schindelin
2007-05-21 3:15 ` Junio C Hamano
2007-05-21 12:56 ` Johannes Schindelin
2007-05-21 18:17 ` Fernando J. Pereda
2007-05-21 18:20 ` Fernando J. Pereda
2007-05-21 23:05 ` [PATCH] Allow user to specify mailbox format for mailsplit Alex Riesen
2007-05-21 23:19 ` Junio C Hamano
2007-05-22 22:04 ` Alex Riesen
2007-05-24 19:47 ` [PATCH] Teach mailsplit about Maildir's Junio C Hamano
2007-05-24 19:56 ` Fernando J. Pereda
2007-05-24 20:12 ` Junio C Hamano
2007-05-24 22:15 ` Fernando J. Pereda
-- strict thread matches above, loose matches on Subject: below --
2007-04-26 19:24 Fernando J. Pereda
2007-04-27 8:30 ` Fernando J. Pereda
2007-04-27 8:54 ` Junio C Hamano
2007-04-27 8:59 ` Fernando J. Pereda
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=200705202127.17723.johan@herland.net \
--to=johan@herland.net \
--cc=ferdy@ferdyx.org \
--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).