From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: multiple machine tagging
Date: Thu, 20 May 2010 12:28:05 -0400 [thread overview]
Message-ID: <87aaru5yi2.fsf@jhu.edu> (raw)
In-Reply-To: <87vdaj2d4p.fsf@ut.hh.sledj.net>
On Thu, 20 May 2010 09:25:42 +0100, David Edmondson <dme@dme.org> wrote:
> What's the current state of the art in merging tags from multiple
> machines?
About the same, I think. I had started trying to figure out a way to do a
smarter dump (only dumping changed info) for my distributed
tagging/bug-tracking idea, and had some early success, though the python
implementation kills some of the speed gains. (Do play with it though!)
But in your case, dumping probably isn't the lag so much as restoring,
right?
What about:
nm dump master>master-dump; nm dump copy >copy-dump;
diff copy-dump master-dump | grep "^>" | etc...
This could all be scripted with scp or curl to do the networking
between machines.
Smarter (history- and namespace-aware) dumping could only improve this,
of course, and is very possible. But the abovr approach seems like it
would remove the restore bottleneck (unless I misunderstand how restore
works with unlisted messages).
Best,
Jesse
next prev parent reply other threads:[~2010-05-20 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 8:25 multiple machine tagging David Edmondson
2010-05-20 16:28 ` Jesse Rosenthal [this message]
2014-09-15 13:49 ` David Edmondson
2014-09-15 14:14 ` W. Trevor King
2014-09-15 14:26 ` David Edmondson
2014-09-15 15:30 ` W. Trevor King
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=87aaru5yi2.fsf@jhu.edu \
--to=jrosenthal@jhu.edu \
--cc=dme@dme.org \
--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).