1 Return-Path: <jrollins@finestructure.net>
\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 DDA4940450F
\r
6 for <notmuch@notmuchmail.org>; Fri, 13 Jan 2012 12:53:04 -0800 (PST)
\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 goJPNmO5AnbF for <notmuch@notmuchmail.org>;
\r
16 Fri, 13 Jan 2012 12:53:04 -0800 (PST)
\r
17 Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu
\r
19 by olra.theworths.org (Postfix) with ESMTP id 4893441439B
\r
20 for <notmuch@notmuchmail.org>; Fri, 13 Jan 2012 12:53:04 -0800 (PST)
\r
21 Received: from earth-doxen.imss.caltech.edu (localhost [127.0.0.1])
\r
22 by earth-doxen-postvirus (Postfix) with ESMTP id 91D9A66E00FF;
\r
23 Fri, 13 Jan 2012 12:52:59 -0800 (PST)
\r
24 X-Spam-Scanned: at Caltech-IMSS on earth-doxen by amavisd-new
\r
25 Received: from finestructure.net (DHCP-123-180.caltech.edu [131.215.123.180])
\r
26 (Authenticated sender: jrollins)
\r
27 by earth-doxen-submit (Postfix) with ESMTP id 92C4A66E0155;
\r
28 Fri, 13 Jan 2012 12:52:49 -0800 (PST)
\r
29 Received: by finestructure.net (Postfix, from userid 1000)
\r
30 id 54BA46E; Fri, 13 Jan 2012 12:52:49 -0800 (PST)
\r
31 From: Jameson Graef Rollins <jrollins@finestructure.net>
\r
32 To: David Bremner <david@tethera.net>, Pieter Praet <pieter@praet.org>,
\r
33 notmuch@notmuchmail.org
\r
34 Subject: Re: revised patch for gmime init, with test.
\r
35 In-Reply-To: <874nw0nfa8.fsf@zancas.localnet>
\r
36 References: <1325306261-21444-2-git-send-email-kaz.rag@gmail.com>
\r
37 <1325388169-8444-1-git-send-email-david@tethera.net>
\r
38 <871ur4ltnx.fsf@praet.org> <877h0wnu1l.fsf@zancas.localnet>
\r
39 <874nw0nfa8.fsf@zancas.localnet>
\r
40 User-Agent: Notmuch/0.10.2+168~g34b8bac (http://notmuchmail.org) Emacs/23.3.1
\r
41 (x86_64-pc-linux-gnu)
\r
42 Date: Fri, 13 Jan 2012 12:52:48 -0800
\r
43 Message-ID: <87ty3ziau7.fsf@servo.finestructure.net>
\r
45 Content-Type: multipart/signed; boundary="=-=-=";
\r
46 micalg=pgp-sha256; protocol="application/pgp-signature"
\r
47 X-BeenThere: notmuch@notmuchmail.org
\r
48 X-Mailman-Version: 2.1.13
\r
50 List-Id: "Use and development of the notmuch mail system."
\r
51 <notmuch.notmuchmail.org>
\r
52 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
54 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
55 List-Post: <mailto:notmuch@notmuchmail.org>
\r
56 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
57 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
59 X-List-Received-Date: Fri, 13 Jan 2012 20:53:05 -0000
\r
62 Content-Transfer-Encoding: quoted-printable
\r
64 On Fri, 13 Jan 2012 05:05:35 -0400, David Bremner <david@tethera.net> wrote:
\r
65 > I thought about this a bit more, and I agree that at least the release
\r
66 > candidates (basically anything tagged on branch release) ought to be
\r
67 > merged back to master. Since any series of bugfix patches seems to be
\r
68 > cause for a new release candidate, this should avoid the need to have
\r
69 > doubly applied patches.
\r
71 > I'm less convinced about the need to merge every little doc change and
\r
72 > debian packaging change back to master right away. This might be a
\r
73 > purely aesthetic objection; I'm not sure if the extra merge commits
\r
74 > cause any problems for e.g. bisection.
\r
76 Doesn't everything need to be merged into master eventually anyway? It
\r
77 seems to me that unless it's a change that very narrowly targeting an
\r
78 issue in a release branch that is not an issue in master, every patch
\r
79 will ultimately need to be applied to both. It doesn't really make
\r
80 sense to me to apply a change to one branch and not the other, if they
\r
81 will eventually need to be applied to both anyway.
\r
86 Content-Type: application/pgp-signature
\r
88 -----BEGIN PGP SIGNATURE-----
\r
89 Version: GnuPG v1.4.11 (GNU/Linux)
\r
91 iQIcBAEBCAAGBQJPEJmhAAoJEO00zqvie6q8fyEQAKHp8cM8tcGzrM6cy4BotSqJ
\r
92 xCCnTQ90qigr4xVkH5glNQJ58XSdV5OAh10Vs+aBSfdmvJVmOqFnfI6W9+zfOIL4
\r
93 aCMz1ez56eB3kj0lnZL7t+fPwV+6WFNa20Zq37Z5nUzj7gPvk5RLL/U27V4mHleq
\r
94 nQpczaiqKy22OURyvl+hnRICod5fGL5B7vp7C8c2m2NfAfcmspa7FhMsUDs2tGs6
\r
95 1FWaWEcgvCBKtTweJBrVDqp5ixd8sth1ShvYCqbRzyqa9x6Vjg6tlc5UhnZWmy1U
\r
96 T0XPEg9NOjIc+muuVAN1C5wqDzpr0VcTBQXNoB6o021YOLLS5I7xt1+bq2F/7mNy
\r
97 Bf7BZVQlJdVvGR0oDy00kFqEW7MvOPLNE1t/VPy+4TDIDRazzW6ZHJ9OgR1b9iXs
\r
98 XI5VhvGUpW1vyowe/REX9m6Yda511zucigQWfIXmrJMPjnlWsJ6Z6kfV8iDLo1Bs
\r
99 Kgr5cfNhDwPCHw+B3lpIQmVlVoZZFerImxTmqqivXchC0aIFMyFK6CVIkJRpt9tI
\r
100 tqG//ZYz0ZYNk8aqCjLmnZMaafC9dRvmzSXXtMHXaVEveGm3vkthEltQjDMVHBu3
\r
101 T+czbfrNYzILnXw2lvyGEgRo/0tkfg4BcsNSPUb6xvMdROwMBW12+q98KsAarzXG
\r
102 MjM0Kk/xBoyLPsuRXScb
\r
104 -----END PGP SIGNATURE-----
\r