From: David Mazieres <dm-list-email-notmuch@scs.stanford.edu>
To: David Bremner <david@tethera.net>,
Brian Sniffen <bsniffen@akamai.com>,
notmuch@notmuchmail.org
Subject: Re: Synchronization success stories?
Date: Fri, 11 Apr 2014 11:02:01 -0700 [thread overview]
Message-ID: <8738hj3fty.fsf@ta.scs.stanford.edu> (raw)
In-Reply-To: <87d2go5cyr.fsf@zancas.localnet>
David Bremner <david@tethera.net> writes:
> Brian Sniffen <bsniffen@akamai.com> writes:
>
>> I'm thrilled by using notmuch to manage my mail. Low-latency search is
>> very important to me. But I use computers in a couple of
>> places---several of which are laptops. Has anyone stories to share of
>> successful multi-computer notmuch sync, for a corpus of a
>> quarter-million messages or so?
>
> I use syncmaildir to sync the actual messages, and a copy of the output
> of "notmuch dump" in git to sync the metadata.
>
> It works OK. A bit slow; depends how often you need to fetch new mail.
If you want to see my solution, it is here:
http://www.scs.stanford.edu/~dm/muchsync-0.tar.gz
I'm a little embarrassed by this code, as I just started to test it a
week ago then instantly became completely dependent on it. I will
probably change the name (from muchsync to syncmuch) and the database
format before releasing. But if you feel like beta-testing and giving
me feedback, have a look.
Beware that if you have been using notmuch dump, you may become
instantly hooked on my solution...
David
next prev parent reply other threads:[~2014-04-11 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 18:51 Synchronization success stories? Brian Sniffen
2014-04-11 11:21 ` David Bremner
2014-04-11 18:02 ` David Mazieres [this message]
2014-04-14 3:56 ` Brian Sniffen
2014-04-13 11:53 ` Tilmann Singer
2014-04-13 12:51 ` David Bremner
2014-04-15 22:55 ` Tilmann Singer
2014-04-13 15:23 ` David Mazieres
2014-04-13 19:08 ` Tilmann Singer
2014-04-13 19:52 ` dm-list-email-notmuch
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738hj3fty.fsf@ta.scs.stanford.edu \
--to=dm-list-email-notmuch@scs.stanford.edu \
--cc=bsniffen@akamai.com \
--cc=david@tethera.net \
--cc=mazieres-tpcbf4ec5tpkktx8p7y7h5uvwi@temporary-address.scs.stanford.edu \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).