Re: [sup-devel] Adding backward synchronization for Maildir sources

["Edward Z. Yang" <ezyang@MIT.EDU>]

Excerpts from Damien Leone's message of Fri Jul 09 13:14:58 -0400 2010:
> > 1. Suppose we decide to test your branch, and run into some show-stopper
> >    bugs.  What’s the procedure for backing out changes?
> 
> You should backup your Maildir directories and your xapian index, this
> is what I did and if something goes wrong I can still restore my
> backups and run offlineimap to resynch everything as it was before on
> the IMAP server.
> 
> But for my initial tests I used a test Maildir containing nothing
> important so maybe this is what you should do. ;)

I doubt a test Maildir will give you the sort of test pressure that you’re
looking for. Go go real datasets.

> > 2. What precisely are the semantics for handling Sup labels?
> 
> I followed the Maildir documentation [0]. When synching a message, Sup
> builds the flags string and relink the file to the disk, moving it
> from new/ to cur/ or vice versa if needed.
> 
> Related labels are: unread, replied, forwarded, deleted, draft (but it
> won't work for now because draft messages in Sup are handled
> separately), flagged (aka starred).

Great, thanks!  I’ll give it a spin this weekend.

Edward
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel