From: Damien Leone <damien.leone@fensalir.fr>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Adding backward synchronization for Maildir sources
Date: Tue, 20 Jul 2010 11:45:41 +0200 [thread overview]
Message-ID: <1279618822-sup-4912@mailer> (raw)
In-Reply-To: <1279493200-sup-3095@ezyang>
[-- Attachment #1.1: Type: text/plain, Size: 1202 bytes --]
Hi,
Excerpts from Edward Z. Yang's message of Mon Jul 19 00:50:39 +0200 2010:
> I would recommend having some sort of flag like 'sync-back'd' programatically
> generated by sup-sync-back-maildir so that Sup will refuse to start if
> you turned on sync-backs without running this command.
Good idea, that might prevent some bad suprises.
> It seems to me that merging the Maildir flags and the Sup flags would
> let you preserve this, but for heavy Sup users this isn't a big deal.
True, and that could be done by sup-sync-back-maildir.
> I think this will be a pretty killer feature to have, because it means
> we can then assign "primary" tags and use those to have sync-backs move
> messages between Maildir folders (on the same account, I imagine), which
> would translate into a folder-sorted webmail view, which is about the
> best you can do without first-class label support in Maildir. I know of
> at least one friend who this would be a deal-maker.
And that doesn't seem hard to implement, we should definitely consider
this feature, maybe after the primary code has been stabilized.
Cheers,
--
Damien Leone <damien.leone@fensalir.fr>
Web: http://dleone.fensalir.fr/
GPG: 0x82EB4DDF
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-07-20 9:52 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
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 [this message]
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=1279618822-sup-4912@mailer \
--to=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