From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] New to Sup and some imap sync questions
Date: Wed, 29 Apr 2009 14:38:13 -0400 [thread overview]
Message-ID: <1241030207-sup-8690@javelin> (raw)
In-Reply-To: <1241028139-sup-8070@entry>
Excerpts from William Morgan's message of Wed Apr 29 14:09:16 -0400 2009:
> Recently I've been thinking about the possibility of storing one's
> mbox/Maildir in git, syncing it between machines (Maildir would probably
> work best for this, as mbox will generate spurious conflicts when
> deleting+adding), and maintaining the Ferret index locally on each
> machine. If we add a notion of an outbound message queue to Sup (i.e.
> each machine knows whether it has the ability to send mail or not), and
> also synchronize that and the drafts and sent folders between machines,
> you could use Sup for completely offline, distributed email. Crazy?
I was under the impression that the interesting stuff (e.g. tags) was
stored in the index, so you would have to sync that too?
Cheers,
Edward
next prev parent reply other threads:[~2009-04-29 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 17:49 Christopher Bertels
2009-04-29 17:04 ` Edward Z. Yang
2009-04-29 18:09 ` William Morgan
2009-04-29 18:38 ` Edward Z. Yang [this message]
2009-04-29 20:16 ` William Morgan
2009-04-29 20:58 ` William Morgan
2009-04-29 20:48 ` Christopher Bertels
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=1241030207-sup-8690@javelin \
--to=ezyang@mit.edu \
/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