From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] now in next: maildir and index version bump
Date: Wed, 26 May 2010 23:31:04 -0400 [thread overview]
Message-ID: <1274847527-sup-4673@zyrg.net> (raw)
I've merged the maildir branch to next. These changes allow Sup to
handle maildirs where messages are being moved and deleted. There are
still some UI fixes I need to make to handle moved/deleted messages
smoothly, but I'm hoping that with the current code there aren't any
regressions.
The maildir branch changes the how message locations are stored so
you'll have to do a full sync after upgrading. I've made sure of this by
incrementing the index version number. This is the first incompatible
index format change since switching to xapian, so I've taken the
opportunity to remove old compatibility code and make some improvements
to sup-dump. The sup-dump in next will work against any older
xapian-based index, so there's no need to downgrade to run it. It will
also work against newer index versions unless the basic structure
changes.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2010-05-27 3:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1274847527-sup-4673@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