From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Possible problem with maildir ID generation
Date: Wed, 29 Apr 2009 15:39:31 -0700 [thread overview]
Message-ID: <1241044743-sup-2889@entry> (raw)
In-Reply-To: <1241038730-sup-2939@entry>
Reformatted excerpts from William Morgan's message of 2009-04-29:
> A timestamp is the obvious choice, but messages can have the same
> timestamp, so then what do you do? The current approach is to sort by
> another arbitrary field (in this cae, message size), which gives a
> unique ordering, but doesn't match up
Sigh.
Doesn't match up with that procmail, or whatever MUA, is giving us.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-04-29 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 22:05 Mark Alexander
2009-04-21 14:00 ` William Morgan
2009-04-21 15:33 ` Mark Alexander
[not found] ` <20090428191822.GB10581@cabinet.hsd1.ma.comcast.net>
2009-04-28 23:29 ` Mark Alexander
2009-04-29 22:31 ` William Morgan
2009-04-29 22:39 ` William Morgan [this message]
[not found] ` <20090429233820.GA14143@cabinet.hsd1.ma.comcast.net>
2009-05-04 16:10 ` William Morgan
[not found] ` <20090504165224.GA15815@cabinet.hsd1.ma.comcast.net>
2009-05-04 17:24 ` Mark Alexander
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=1241044743-sup-2889@entry \
--to=wmorgan-sup@masanjin.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