From: David Bremner <david@tethera.net>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	Daniel Schoepe <daniel@schoepe.org>, notmuch@notmuchmail.org
Subject: Re: Patch review/application process
In-Reply-To: <87sjm74z36.fsf@servo.finestructure.net>
References: <878vo8kdl2.fsf@gilead.invalid> <87hb2n7w82.fsf@zancas.localnet>
	<87sjm74z36.fsf@servo.finestructure.net>
User-Agent: Notmuch/0.9+29~g4efaa70 (http://notmuchmail.org) Emacs/23.3.1
	(x86_64-pc-linux-gnu)
Date: Tue, 01 Nov 2011 16:55:03 -0300
Message-ID: <87vcr3ehyg.fsf@convex-new.cs.unb.ca>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Tue, 01 Nov 2011 08:55:09 -0700, Jameson Graef Rollins <jrollins@finestr=
ucture.net> wrote:
> On Tue, 01 Nov 2011 11:28:45 -0300, David Bremner <david@tethera.net> wro=
te:
> > Maybe you can tag those patches as "notmuch::reviewed" using nmbug? [1]
> > My idea is that=20
> >=20
> >    notmuch search tag:notmuch::patch and tag:notmuch::reviewed
> >=20
> > should give a kind of consensus set of "ready to go" patch sets.
>=20
> Don't forget notmuch::applied, which I think is actually one of the most
> important.  Review is easy to see by looking at the patch thread.  Being
> able to easily find which patches have not yet been applied to master is
> what I'm most looking forward to.

Jamie knows this from IRC, but I have been using "notmuch::pushed" for
this.

One thing I think we need to clarify a bit is are we tagging whole
threads or individual messages in the database.  Because of the way
notmuch search works, I had been tagging whole threads with
notmuch::pushed (effectively to "mute" them) in the search

                notmuch search tag:notmuch::patch and \
                        not tag:notmuch::pushed

This is a bit aesthetically unappealing, anad every time someone replies
to a thread it is effectively unmuted.

Since we don't have thread tagging yet (where e.g. tags are
automagically applied to new messages I was thinking it might work have
a tag like "notmuch::todo" and something like the following workflow
(for patches)

initially tag +notmuch::patch +notmuch::todo

then when we "dispose" of the patch somehow, remove the notmuch::todo tag a=
nd
replace with
        notmuch::pushed
        notmuch::obsolete
        or...

Then we could do e.g.

     notmuch search tag:notmuch::patch and tag:notmuch::todo and tag:notmuc=
h::reviewed

to get an "integrators queue" (Well, the more like an unordered pile
than a queue. One problem at a time).

David





--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iJwEAQECAAYFAk6wTpcACgkQTiiN/0Um85lfuQQAs1yp/yTYM7ji1YXRlNKhxcK3
Skd70H44CNapyk9kUESwd9gGTnzrbFleLKR0k6GdNt07Pvo+wX7/1Nmck7K4lhXP
84bSq4u89iF/QU/qaTJzDV92wNsNExZf+nZPbr51dmKLF6z9UfxlubAR/Kw/S6M6
KNBUwxsvHpISFCxsa40=
=jHKq
-----END PGP SIGNATURE-----
--=-=-=--