From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Damien Leone <damien.leone@fensalir.fr>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Adding backward synchronization for Maildir sources
Date: Fri, 09 Jul 2010 15:46:08 -0400 [thread overview]
Message-ID: <1278704722-sup-2256@ezyang> (raw)
In-Reply-To: <1278695023-sup-8869@mailer>
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
next prev parent reply other threads:[~2010-07-09 20:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 16:44 Damien Leone
2010-07-09 16:56 ` Edward Z. Yang
2010-07-09 17:14 ` Damien Leone
2010-07-09 19:46 ` Edward Z. Yang [this message]
2010-07-17 12:55 ` Damien Leone
2010-07-17 17:05 ` Ben Walton
2010-07-17 17:26 ` Damien Leone
2010-07-18 11:19 ` Tero Tilus
2010-07-18 22:46 ` Edward Z. Yang
2010-07-20 9:39 ` Damien Leone
2010-07-21 0:44 ` Edward Z. Yang
2010-07-21 8:52 ` Damien Leone
2010-07-21 8:54 ` Damien Leone
2010-07-18 22:50 ` Edward Z. Yang
2010-07-20 9:45 ` Damien Leone
2010-07-18 22:57 ` Edward Z. Yang
2010-07-24 21:30 ` Rich Lane
2010-07-25 22:25 ` Edward Z. Yang
2011-03-13 16:41 ` Damien Leone
2011-10-27 12:34 ` Justin Mazzi
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=1278704722-sup-2256@ezyang \
--to=ezyang@mit.edu \
--cc=damien.leone@fensalir.fr \
--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