From: David Bremner <david@tethera.net>
To: David Mazieres expires 2014-07-10 PDT
	<mazieres-7je64uqare55j4eig77r2axtva@temporary-address.scs.stanford.edu>,
	Gaute Hope <eg@gaute.vetsj.com>
Subject: Re: [PATCH] Add configurable changed tag to messages that have been
	changed on disk
In-Reply-To: <877g6v3lb9.fsf@ta.scs.stanford.edu>
References: <1396800683-9164-1-git-send-email-eg@gaute.vetsj.com>
	<87wqf2gqig.fsf@ta.scs.stanford.edu> <1397140962-sup-6514@qwerzila>
	<87wqexnqvb.fsf@ta.scs.stanford.edu> <87k3aw5dj5.fsf@zancas.localnet>
	<877g6v3lb9.fsf@ta.scs.stanford.edu>
User-Agent: Notmuch/0.17+180~g8977b1a (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-pc-linux-gnu)
Date: Sat, 12 Apr 2014 12:58:29 -0300
Message-ID: <87mwfq4k0q.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain
Cc: notmuch <notmuch@notmuchmail.org>
Precedence: list

dm-list-email-notmuch@scs.stanford.edu writes:

>
> As far as updating the test suite, etc., it's almost certain that the
> core notmuch developers would be unsatisfied with whatever I've done,
> since the code base is very clean and has a very uniform style.  So when
> I say I'd want some "indication that such a change could be upstreamed,"
> I mean more specifically that someone would be willing to shepherd the
> process of getting the code into shape.
>

I think it depends on your definition of shepherd. If it means review
your patches and tell you what needs to be done, then we can probably
handle that. Things tend to stall if the patch proposer loses interest
after the first review, so we're pretty far from "fire and forget".

I'd like to hear one or two more opinions from regular contributors
before I say "yes, this is something we want to do."

cheers,

d