Re: What's cooking in git.git (Nov 2012, #02; Fri, 9)

From: Jeff King <peff@peff.net>
Date: Nov 10, 2012, 00:38 UTC
Message-ID: <20121110003850.GB12567@sigill.intra.peff.net>
In-Reply-To: <7vr4o2plmw.fsf@alter.siamese.dyndns.org>

On Fri, Nov 09, 2012 at 12:27:35PM -0800, Junio C Hamano wrote:

Show 14 quoted lines

> Jeff King <peff@peff.net> writes:
> 
> > I have not been pushing the individual topic branches to make life
> > easier for people who usually just track Junio's kernel.org repository,
> > and would not welcome suddenly getting a hundred extra remote branches.
> > I can make them public if it makes life easier for people, but it may
> > not be worth it at this point, with Junio returning soon.
> 
> What we should have arranged was to have https://github.com/git/git
> (which is not even owned by me, but I asked somebody at GitHub to
> assign me a write privilege) writable by the interim maintainer, so
> that normal people would keep pulling from there, while the interim
> maintainer can choose to publish broken-out branches to his
> repository.

Yes, I have write access to that repository, too, but I intentionally held off from updating it out of a sense of nervousness. I figured if I screwed up anything too badly, people who were clued-in enough to switch to pulling from my repository would be clued-in enough to rebase across any too-horrible mistake I made. ;)

I think if we do this again, I will make the same split you do (git/git for integration branches, peff/git as a mirror of my private repo).

> And it is not too late to do so; from the look of your "What's
> cooking", you are doing pretty well ;-).

Any fool can merge topics to master. The real test will be how many regressions people report in the next two weeks. :)

By the way, I did not touch 'maint' at all while you were gone. I don't know what your usual method is for keeping track of maint-worthy topics after they have gone to master. The usual "what's cooking" workflow keeps track of things going to master, but no more; I'd guess you probably just merge to maint when you delete them from last cycle's "graduated to master" list.

I just let them stew in master for a bit longer, and we can easily find and merge them with "git branch --no-merged maint | grep maint".

-Peff