From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] New to Sup and some imap sync questions
Date: Wed, 29 Apr 2009 13:58:01 -0700 [thread overview]
Message-ID: <1241038425-sup-3748@entry> (raw)
In-Reply-To: <1241036141-sup-3541@entry>
Reformatted excerpts from William Morgan's message of 2009-04-29:
> That would have to be update to include all new messages every time
> you synced. And the flags would have to be synced too. Not a trivial
> undertaking, but within the realm of possibility.
That wasn't very clear. Let me try again. The Ferret index (a scary
binary thing) would not be synced. Individual sources would be synced,
along with some version of the message flags (probably as a
newline-separated text file, to allow conflict resolution (!)), and then
the index would be updated on the local machine to reflect those
changes.
Kinda tantamount to rsyncing your .sup directory and all your sources
across different machines, but a little more refined.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-04-29 20:58 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
2009-04-29 20:16 ` William Morgan
2009-04-29 20:58 ` William Morgan [this message]
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=1241038425-sup-3748@entry \
--to=wmorgan-sup@masanjin.net \
/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