Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Fwd: Automatic labels backup
Date: Mon, 21 Dec 2009 08:35:44 -0800	[thread overview]
Message-ID: <1261412908-sup-5527@masanjin.net> (raw)
In-Reply-To: <1261265869-sup-7604@kronos>

Reformatted excerpts from William Baxter's message of 2009-12-19:
> How much additional work does it take to turn an index dump into a
> sup-to-sup sync mechanism?  Suppose that on one host you dump the
> index and send a signed message.  This reaches the receiving host when
> you read mail there.  Use it to update the index, and the receiving
> host has labels matching those on the sending host.

It might not be fast or pretty, but should be easy. To sync an index
on computer B based on a dump from computer A, you should be able to
just:

computer B> sup-sync --restore <dumpfile from A>

That should both a) load any new messages from the source, and b) update
them with the labels from the dumpfile.

It's a little silly because you're transmitting the dumpfile for the
entire index back and forth between the two. If it were ordered, you
could just take a portion of it.

I've never tried this, but based on a visual inspection of the code, I
Guarantee It Works (tm).
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      reply	other threads:[~2009-12-21 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15  5:35 Edward Z. Yang
2009-12-19 19:02 ` William Morgan
2009-12-19 19:13   ` Edward Z. Yang
2009-12-19 23:57 ` William Baxter
2009-12-21 16:35   ` William Morgan [this message]

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=1261412908-sup-5527@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --cc=sup-talk@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