1 Return-Path: <bremner@unb.ca>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 7BD42431FB6
\r
6 for <notmuch@notmuchmail.org>; Tue, 1 Nov 2011 12:55:38 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id ERqagqeaAFjc for <notmuch@notmuchmail.org>;
\r
16 Tue, 1 Nov 2011 12:55:38 -0700 (PDT)
\r
17 Received: from tempo.its.unb.ca (tempo.its.unb.ca [131.202.1.21])
\r
18 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id CF440431FD0
\r
21 for <notmuch@notmuchmail.org>; Tue, 1 Nov 2011 12:55:37 -0700 (PDT)
\r
22 Received: from convex-new.cs.unb.ca ([131.202.13.154])
\r
23 by tempo.its.unb.ca (8.13.8/8.13.8) with ESMTP id pA1JtNC9019852;
\r
24 Tue, 1 Nov 2011 16:55:23 -0300
\r
25 Received: from bremner by convex-new.cs.unb.ca with local (Exim 4.72)
\r
26 (envelope-from <bremner@unb.ca>)
\r
27 id 1RLKQc-0007RY-Vv; Tue, 01 Nov 2011 16:55:22 -0300
\r
28 From: David Bremner <david@tethera.net>
\r
29 To: Jameson Graef Rollins <jrollins@finestructure.net>,
\r
30 Daniel Schoepe <daniel@schoepe.org>, notmuch@notmuchmail.org
\r
31 Subject: Re: Patch review/application process
\r
32 In-Reply-To: <87sjm74z36.fsf@servo.finestructure.net>
\r
33 References: <878vo8kdl2.fsf@gilead.invalid> <87hb2n7w82.fsf@zancas.localnet>
\r
34 <87sjm74z36.fsf@servo.finestructure.net>
\r
35 User-Agent: Notmuch/0.9+29~g4efaa70 (http://notmuchmail.org) Emacs/23.3.1
\r
36 (x86_64-pc-linux-gnu)
\r
37 Date: Tue, 01 Nov 2011 16:55:03 -0300
\r
38 Message-ID: <87vcr3ehyg.fsf@convex-new.cs.unb.ca>
\r
40 Content-Type: multipart/signed; boundary="=-=-=";
\r
41 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
42 X-BeenThere: notmuch@notmuchmail.org
\r
43 X-Mailman-Version: 2.1.13
\r
45 List-Id: "Use and development of the notmuch mail system."
\r
46 <notmuch.notmuchmail.org>
\r
47 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
48 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
49 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
50 List-Post: <mailto:notmuch@notmuchmail.org>
\r
51 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
52 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
54 X-List-Received-Date: Tue, 01 Nov 2011 19:55:38 -0000
\r
57 Content-Transfer-Encoding: quoted-printable
\r
59 On Tue, 01 Nov 2011 08:55:09 -0700, Jameson Graef Rollins <jrollins@finestr=
\r
61 > On Tue, 01 Nov 2011 11:28:45 -0300, David Bremner <david@tethera.net> wro=
\r
63 > > Maybe you can tag those patches as "notmuch::reviewed" using nmbug? [1]
\r
64 > > My idea is that=20
\r
66 > > notmuch search tag:notmuch::patch and tag:notmuch::reviewed
\r
68 > > should give a kind of consensus set of "ready to go" patch sets.
\r
70 > Don't forget notmuch::applied, which I think is actually one of the most
\r
71 > important. Review is easy to see by looking at the patch thread. Being
\r
72 > able to easily find which patches have not yet been applied to master is
\r
73 > what I'm most looking forward to.
\r
75 Jamie knows this from IRC, but I have been using "notmuch::pushed" for
\r
78 One thing I think we need to clarify a bit is are we tagging whole
\r
79 threads or individual messages in the database. Because of the way
\r
80 notmuch search works, I had been tagging whole threads with
\r
81 notmuch::pushed (effectively to "mute" them) in the search
\r
83 notmuch search tag:notmuch::patch and \
\r
84 not tag:notmuch::pushed
\r
86 This is a bit aesthetically unappealing, anad every time someone replies
\r
87 to a thread it is effectively unmuted.
\r
89 Since we don't have thread tagging yet (where e.g. tags are
\r
90 automagically applied to new messages I was thinking it might work have
\r
91 a tag like "notmuch::todo" and something like the following workflow
\r
94 initially tag +notmuch::patch +notmuch::todo
\r
96 then when we "dispose" of the patch somehow, remove the notmuch::todo tag a=
\r
103 Then we could do e.g.
\r
105 notmuch search tag:notmuch::patch and tag:notmuch::todo and tag:notmuc=
\r
108 to get an "integrators queue" (Well, the more like an unordered pile
\r
109 than a queue. One problem at a time).
\r
118 Content-Type: application/pgp-signature
\r
120 -----BEGIN PGP SIGNATURE-----
\r
121 Version: GnuPG v1.4.10 (GNU/Linux)
\r
123 iJwEAQECAAYFAk6wTpcACgkQTiiN/0Um85lfuQQAs1yp/yTYM7ji1YXRlNKhxcK3
\r
124 Skd70H44CNapyk9kUESwd9gGTnzrbFleLKR0k6GdNt07Pvo+wX7/1Nmck7K4lhXP
\r
125 84bSq4u89iF/QU/qaTJzDV92wNsNExZf+nZPbr51dmKLF6z9UfxlubAR/Kw/S6M6
\r
126 KNBUwxsvHpISFCxsa40=
\r
128 -----END PGP SIGNATURE-----
\r