From: James Westby <jw+debian@jameswestby.net>
To: martin f krafft <madduck@madduck.net>, Jameson Rollins
	<jrollins@finestructure.net>
In-Reply-To: <20100128051252.GB12540@lapse.rw.madduck.net>
References: <20100125162247.85F0F66FA8@aether.pioto.org>
	<87tyu9dfhs.fsf@servo.finestructure.net> <1264523377-sup-6110@elise>
	<87aaw0vlvp.fsf@servo.finestructure.net>
	<20100128051252.GB12540@lapse.rw.madduck.net>
Date: Thu, 28 Jan 2010 18:28:38 +1300
Message-ID: <87k4v2re61.fsf@jameswestby.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [notmuch] tag dir proposal [was: Re: Git as notmuch object
 store]
Precedence: list

On Thu, 28 Jan 2010 18:12:52 +1300, martin f krafft <madduck@madduck.net> wrote:
> also sprach Jameson Rollins <jrollins@finestructure.net> [2010.01.27.0603 +1300]:
> > > 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?
> > 
> > I think this idea is completely independent of anything having to do
> > with using git as a mail store.  That's why I was trying to separate it
> > into a separate thread.
> 
> I think he meant "notmuch hooks like you have hooks for Git too",
> e.g. thread:755741d13573c7642761d2a175cb146d

Are you trying to use thread: such that it could be passed to notmuch
show to see the conversation?

That's not going to work so well if so.

Thanks,

James