From: Mark Alexander <marka@pobox.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Maildir work
Date: Wed, 10 Feb 2010 15:50:42 -0500 [thread overview]
Message-ID: <a412e2a71002101250hff7efa3i1290c01ba8874f81@mail.gmail.com> (raw)
In-Reply-To: <6c0c31751002091239g6002c7fl6bfa93908c4d4301@mail.gmail.com>
On Tue, Feb 9, 2010 at 3:39 PM, Scott Henson <scott@foolishpride.org> wrote:
>The maildir source can easily lose messages because there is nothing guaranteeing that
> the source_id is monotonically increasing.
I reported this on Apr 16 2009:
http://old.nabble.com/Possible-problem-with-maildir-ID-generation-ts23087464.html
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-02-10 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 20:39 Scott Henson
2010-02-09 21:33 ` Ben Walton
2010-02-10 20:50 ` Mark Alexander [this message]
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=a412e2a71002101250hff7efa3i1290c01ba8874f81@mail.gmail.com \
--to=marka@pobox.com \
--cc=sup-devel@rubyforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox