From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs208579icb; Thu, 20 Jan 2011 08:07:10 -0800 (PST) Received: by 10.42.170.3 with SMTP id d3mr2787934icz.260.1295539630818; Thu, 20 Jan 2011 08:07:10 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id u11si17184843qco.201.2011.01.20.08.07.10; Thu, 20 Jan 2011 08:07:10 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 2E1F5197833E; Thu, 20 Jan 2011 11:07:10 -0500 (EST) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by rubyforge.org (Postfix) with ESMTP id CF5E81858356 for ; Thu, 20 Jan 2011 10:28:19 -0500 (EST) Received: by wwb31 with SMTP id 31so724916wwb.23 for ; Thu, 20 Jan 2011 07:28:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:subject:to:in-reply-to :references:mime-version:content-type:content-id; bh=2Ggk9otYNDIwQvqGE6vd7ZyJqC/v0fEemtDz1kx/XSA=; b=XJxfUNdNrAOGqCOWL84HW64C/Das2qDF7O7a3qJ04P1U4gbGPZ0nrV6g1p6TMGf65P 8SESa0/5cWwyUjCGKIRVV/sp4Bwc5zbu9G0S8H1lxlJ/ooBq4rbxLJKUChz0KykLgfLD W0M45nA11uFU39WAUn1yx/ANuxrleQl0F2xiA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:subject:to:in-reply-to:references:mime-version :content-type:content-id; b=sV12891LD5cckenV1/Xij4w8KTmPrpYxVJDYJ/mmmfBGHxYroqbt09SZYze8o9D4Zx 5sBMNVRArRAfNm0MP8bFeaOAlQbU3JYipReE1RGds8yr3LAqUibNeLXUBGd74s4sxxVv JxcP384RyTGPSUsMzEBGgO6QGXs94FkUIg7xE= Received: by 10.227.141.209 with SMTP id n17mr2524387wbu.121.1295537299102; Thu, 20 Jan 2011 07:28:19 -0800 (PST) Received: from localhost (sk.feydakins.org [94.23.4.142]) by mx.google.com with ESMTPS id f35sm6086941wbf.8.2011.01.20.07.28.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 20 Jan 2011 07:28:17 -0800 (PST) Message-ID: <4d385491.2308e30a.02b2.ffffd7ce@mx.google.com> Date: Thu, 20 Jan 2011 07:28:17 -0800 (PST) From: Nicolas Pouillard To: Sascha Silbe , Sup developer discussion , sup-devel In-Reply-To: <1295445135-1782-1-git-send-email-sascha-pgp@silbe.org> References: <1281085361-sup-7888@xo15-sascha.sascha.silbe.org> <1295445135-1782-1-git-send-email-sascha-pgp@silbe.org> MIME-Version: 1.0 Content-ID: <32623.1295537295.1@sk.feydakins.org> Subject: Re: [sup-devel] [PATCH] add sup-import-dump: import message state in sup-dump format X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org On Wed, 19 Jan 2011 14:52:15 +0100, Sascha Silbe wrote: > sup-import-dump imports message state as exported by sup-dump into the index. > It is a direct replacement for the sup-sync --restored functionality that got > lost when merging the maildir branch. > Unlike sup-sync it operates on the index only, so it's fast enough for > periodically importing full dumps to keep multiple sup installations > synchronised. So it does not clear the index, right? It only assign the set of labels to the given message. Just what I need to upgrade my sup index with my notmuch index. > It should also be easy enough to add support for a "diff" style format that > would allow replaying "logs" if sup were enhanced to write those in the > future. Please do. I hacked such a logging feature [1] in the past (at the time where sup used ferret and that message loss happened), then I merged the previous index dump with the log and compared this to the actual dump (I wrote some tools to play with this log format). Cheers, [1]: http://gitorious.org/~ertai/sup/clone-by-ertai/commits/to-submit-log-labels-mapping -- Nicolas Pouillard http://nicolaspouillard.fr _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel