Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 2A735431FBC for ; Mon, 11 Jan 2010 19:44:20 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5XB37fgw9Ptc for ; Mon, 11 Jan 2010 19:44:19 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by olra.theworths.org (Postfix) with ESMTP id 4D142431FAE for ; Mon, 11 Jan 2010 19:44:19 -0800 (PST) Received-SPF: pass (mxus2: domain of quadhome.com designates 68.68.99.250 as permitted sender) client-ip=68.68.99.250; envelope-from=scott@quadhome.com; helo=julia.quadhome.com; Received: from julia.quadhome.com (quadhome.xen.prgmr.com [68.68.99.250]) by mx.perfora.net (node=mxus2) with ESMTP (Nemesis) id 0LhPFg-1OGkbK3Flg-00meLj for notmuch@notmuchmail.org; Mon, 11 Jan 2010 22:44:18 -0500 Received: from elise.quadhome.com (localhost [127.0.0.1]) by julia.quadhome.com (Postfix) with ESMTPSA id E9EAE5FBC1 for ; Tue, 12 Jan 2010 03:44:15 +0000 (UTC) Content-Type: text/plain; charset=UTF-8 From: Scott Robinson To: notmuch In-reply-to: <20100111221909.GA30299@lapse.rw.madduck.net> References: <20100111221909.GA30299@lapse.rw.madduck.net> Date: Mon, 11 Jan 2010 21:44:11 -0600 Message-Id: <1263267603-sup-302@elise> User-Agent: Sup/git Content-Transfer-Encoding: 8bit Subject: Re: [notmuch] Idea for storing tags X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2010 03:44:20 -0000 I wrote a script to store and sync my tags. * One filename per message-ID. * Line-feed seperated tags in each file. Then the whole structure is controlled via git. Conflict-resolution and sync comes for free. It isn't clear what use-case the earlier e-mail is aiming to satisfy. This is how I solved my tag sync issues, though.