1 Return-Path: <amit.kucheria@verdurent.com>
\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 78EFE40BFDB
\r
6 for <notmuch@notmuchmail.org>; Mon, 11 Oct 2010 12:41:04 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
\r
12 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
\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 K9-JRWRnINUi for <notmuch@notmuchmail.org>;
\r
16 Mon, 11 Oct 2010 12:40:52 -0700 (PDT)
\r
17 Received: from mail-iw0-f181.google.com (mail-iw0-f181.google.com
\r
19 by olra.theworths.org (Postfix) with ESMTP id D77E340BFD3
\r
20 for <notmuch@notmuchmail.org>; Mon, 11 Oct 2010 12:40:52 -0700 (PDT)
\r
21 Received: by iwn39 with SMTP id 39so1969496iwn.26
\r
22 for <notmuch@notmuchmail.org>; Mon, 11 Oct 2010 12:40:52 -0700 (PDT)
\r
24 Received: by 10.231.159.204 with SMTP id k12mr4942401ibx.42.1286826052313;
\r
25 Mon, 11 Oct 2010 12:40:52 -0700 (PDT)
\r
26 Received: by 10.231.34.9 with HTTP; Mon, 11 Oct 2010 12:40:52 -0700 (PDT)
\r
27 In-Reply-To: <87pqvgr1u5.fsf@servo.finestructure.net>
\r
28 References: <AANLkTimes1ndLhOxJupDh72h1MRR0q28wu7mjAeCOzVu@mail.gmail.com>
\r
29 <87pqvgr1u5.fsf@servo.finestructure.net>
\r
30 Date: Mon, 11 Oct 2010 22:40:52 +0300
\r
31 Message-ID: <AANLkTimNeN_2xJWTvKrR+AhKsyj46Ti75bjaVLx8-hrf@mail.gmail.com>
\r
32 Subject: Re: notmuch-next branch
\r
33 From: Amit Kucheria <amit.kucheria@verdurent.com>
\r
34 To: Jameson Rollins <jrollins@finestructure.net>
\r
35 Content-Type: text/plain; charset=ISO-8859-1
\r
36 Content-Transfer-Encoding: quoted-printable
\r
37 Cc: notmuch@notmuchmail.org
\r
38 X-BeenThere: notmuch@notmuchmail.org
\r
39 X-Mailman-Version: 2.1.13
\r
41 List-Id: "Use and development of the notmuch mail system."
\r
42 <notmuch.notmuchmail.org>
\r
43 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
44 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
45 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
46 List-Post: <mailto:notmuch@notmuchmail.org>
\r
47 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
48 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
50 X-List-Received-Date: Mon, 11 Oct 2010 19:41:04 -0000
\r
52 On Mon, Oct 11, 2010 at 10:01 PM, Jameson Rollins
\r
53 <jrollins@finestructure.net> wrote:
\r
54 > On Mon, 11 Oct 2010 21:45:47 +0300, Felipe Contreras <felipe.contreras@gm=
\r
56 >> I think many people agree notmuch mainline has been rather slow. So
\r
57 >> I'm proposing to have notmuch-next branch, either on github or
\r
58 >> gitorious (please vote).
\r
60 >> More than one person should have write access to this repo, but some
\r
61 >> guidelines should be in place. I propose that patches should be
\r
62 >> signed-off-by at least another person in the mailing list before
\r
63 >> pushing. It would be nice if this is how the mainline branch works,
\r
64 >> but we don't need to wait for that to happen. We need to vote on who
\r
65 >> are the people to have write access.
\r
67 > I think this generally sounds like a fine idea, but I don't see why we
\r
68 > need a single central repo that multiple people need access to. =A0The
\r
69 > whole point of git is to allow for distributed development without need
\r
70 > for a central repo.
\r
72 While distributed development is good, it would be nice for users to
\r
73 be able to clone one git repo instead of tracking 5 different trees.
\r
74 And more users typically means more robust software.
\r
76 It would also make it easier to merge patches back into notmuch-master
\r
77 if it ever takes off again.
\r
79 > In this case, folks can just merge the patches they're interested in
\r
80 > into a "next" branch in their own personal repos, publish them where
\r
81 > ever they want, and then every body can just keep their "next" branches
\r
82 > synced with each other. =A0As consensus is reached, the next release will
\r
85 Everyone can still maintain their own trees. Patches can go into the
\r
86 '-next' repo only after being ack'ed by 1-2 active developers on the
\r
87 mailing list. Meanwhile they bake in personal trees.
\r