From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.87.14 with SMTP id k14cs675671agb; Mon, 21 Dec 2009 08:35:53 -0800 (PST) Received: by 10.224.15.210 with SMTP id l18mr3963001qaa.91.1261413352933; Mon, 21 Dec 2009 08:35:52 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 5si8315780qyk.107.2009.12.21.08.35.52; Mon, 21 Dec 2009 08:35:52 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id B1519185831F; Mon, 21 Dec 2009 11:35:52 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id E6B58185830A for ; Mon, 21 Dec 2009 11:35:44 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NMlEW-0005Zd-P4 for sup-talk@rubyforge.org; Mon, 21 Dec 2009 08:35:44 -0800 From: William Morgan To: sup-talk In-reply-to: <1261265869-sup-7604@kronos> References: <1260855317-sup-863@ezyang> <1261265869-sup-7604@kronos> Date: Mon, 21 Dec 2009 08:35:44 -0800 Message-Id: <1261412908-sup-5527@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] Fwd: Automatic labels backup X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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 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 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk