Re: What's cooking in git.git (Jan 2009, #07; Wed, 28)
- From
Jeff King <peff@peff.net>
- Date
- Jan 30, 2009, 16:26 UTC
- Message-ID
- <20090130162603.GB7065@sigill.intra.peff.net>
- In-Reply-To
- <alpine.DEB.1.00.0901301415260.3586@pacific.mpi-cbg.de>
On Fri, Jan 30, 2009 at 02:18:32PM +0100, Johannes Schindelin wrote:
Show 22 quoted lines
> > You could make a guess that they will use "master", and if you are > > wrong, it behaves as now. But if you are right, "git pull" pulls down > > master automatically. > > > > But that is getting a little confusing. So let's push this "git push > > --track" idea to completion and see how people like it. > > How about installing > > [branch "master"] > remote = origin > merge = refs/heads/master > > by default? It is a safe bet that this will be the case for 99% of all > users that want to clone an empty repository (especially if they are > putting their public repositories on something like repo.or.cz, where you > cannot change the default branch from "master" to something else). > > And if somebody wants to track another branch, tough, she has to call > this: > > $ git checkout -t origin/blablabla
I was tempted to suggest that, but I haven't thought through whether there are any lurking corner cases (which empty clone seems to be fraught with). So I think it is a reasonable thing to try and play with.
-Peff