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 E264F431FBC for ; Tue, 26 Jan 2010 08:32:04 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.674 X-Spam-Level: X-Spam-Status: No, score=0.674 tagged_above=-999 required=5 tests=[AWL=0.673, BAYES_50=0.001] autolearn=ham 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 rP+i3K56i+Gm for ; Tue, 26 Jan 2010 08:32:04 -0800 (PST) X-Greylist: delayed 142318 seconds by postgrey-1.32 at olra; Tue, 26 Jan 2010 08:32:04 PST Received: from julia.quadhome.com (quadhome.xen.prgmr.com [68.68.99.250]) by olra.theworths.org (Postfix) with ESMTP id 5C2D6431FAE for ; Tue, 26 Jan 2010 08:32:04 -0800 (PST) Received: from elise.quadhome.com (localhost [127.0.0.1]) by julia.quadhome.com (Postfix) with ESMTPSA id 62D6A5FC40 for ; Tue, 26 Jan 2010 16:32:03 +0000 (UTC) Content-Type: text/plain; charset=UTF-8 From: Scott Robinson To: notmuch In-reply-to: <87tyu9dfhs.fsf@servo.finestructure.net> References: <20100125162247.85F0F66FA8@aether.pioto.org> <87tyu9dfhs.fsf@servo.finestructure.net> Date: Tue, 26 Jan 2010 10:32:02 -0600 Message-Id: <1264523377-sup-6110@elise> User-Agent: Sup/git Content-Transfer-Encoding: 8bit Subject: Re: [notmuch] tag dir proposal [was: Re: Git as notmuch object store] 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, 26 Jan 2010 16:32:05 -0000 Excerpts from Jameson Rollins's message of Mon Jan 25 15:46:55 -0600 2010: > I think this idea is a really good one and I would like to pursue it as > a tangent thread here. I was going to propose something very similar to > this. I think it's a very flexible idea that would help in a lot of > ways. > > [...] This is getting involved. Maybe I'm missing something in this thread; but, why couldn't these complex and context-sensitive decisions be delegated to sub-processes? ala git hooks?