From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] new branch: maildir
Date: Thu, 25 Mar 2010 03:12:57 -0400 [thread overview]
Message-ID: <1269499582-sup-2593@zyrg.net> (raw)
This branch makes some drastic changes to how mbox and maildir sources
work. There's no longer any state associated with a source between Sup
runs - no cur_offset or mtimes in sources.yaml. Instead, the source
queries the index to find out which messages it's already seen and which
messages are new. This enables a much more robust maildir
implementation that detects the addition or deletion of any message.
It's not totally done yet. It'll detect that a maildir message has been
deleted, but it doesn't yet remove the old location from the index so
renames are unlikely to work. There needs to be UI code to handle the
case where a message matches a search but has been deleted from all
sources, and probably a utility to remove such messages from the index.
I expect sup-sync-back to be broken.
Keeping track of multiple locations per message requires an index format
change. The upgrade process is trivial and done automatically but you
won't be able to use that index with an older Sup. For now if you want
to try this out I suggest using a different SUP_BASE.
I'd appreciate any comments about the code or general approach. If
anyone would like to contribute an email corpus for the unwritten
testsuite or pseudocode out some testcases that would be very helpful
too.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2010-03-25 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 7:12 Rich Lane [this message]
2010-03-25 11:24 ` Mark Alexander
2010-03-25 13:30 ` Ben Walton
2010-03-25 16:11 ` Rich Lane
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=1269499582-sup-2593@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--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