notmuch-next branch

Jameson Rollins jrollins at finestructure.net
Mon Oct 11 12:01:06 PDT 2010


On Mon, 11 Oct 2010 21:45:47 +0300, Felipe Contreras <felipe.contreras at gmail.com> wrote:
> I think many people agree notmuch mainline has been rather slow. So
> I'm proposing to have notmuch-next branch, either on github or
> gitorious (please vote).
> 
> More than one person should have write access to this repo, but some
> guidelines should be in place. I propose that patches should be
> signed-off-by at least another person in the mailing list before
> pushing. It would be nice if this is how the mainline branch works,
> but we don't need to wait for that to happen. We need to vote on who
> are the people to have write access.

I think this generally sounds like a fine idea, but I don't see why we
need a single central repo that multiple people need access to.  The
whole point of git is to allow for distributed development without need
for a central repo.

In this case, folks can just merge the patches they're interested in
into a "next" branch in their own personal repos, publish them where
ever they want, and then every body can just keep their "next" branches
synced with each other.  As consensus is reached, the next release will
emerge.

jamie.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20101011/b1e06538/attachment.pgp>


More information about the notmuch mailing list