Re: [PATCH] push: Learn to set up branch tracking with '--track'

From: Jeff King <peff@peff.net>
Date: Feb 6, 2009, 14:10 UTC
Message-ID: <20090206141000.GC18364@coredump.intra.peff.net>
In-Reply-To: <alpine.DEB.1.00.0902021449370.3586@pacific.mpi-cbg.de>

On Mon, Feb 02, 2009 at 02:52:26PM +0100, Johannes Schindelin wrote:

Show 15 quoted lines

> > It looks like the consensus is to add a branch.master config section 
> > even when cloning an empty repo. And that should address my concern in 
> > the 99% of cases where people use the default "master" setup. Which kind 
> > of takes away the main use case for this topic.
> 
> From where I sit, the main use would have been:
> 
> 	# <hackhackhack>
> 	$ git init
> 	$ git add .
> 	$ git commit -m initial\ revision
> 	# <hackhackhack>
> 	# <create a repository on repo.or.cz>
> 	$ git remote add origin $URL
> 	$ git push -t origin master

Hmm. True. The "clone empty" fix only affects people who use the "init; clone empty; push" method. Push-tracking would work for the "traditional" method you outline above.

So probably it is worth doing the steps I described earlier. I'll throw it on my todo list, but the priority is not especially high.

> BTW I always wondered if it would make sense to introduce "git commit 
> --init" for the first 3 Git commands.  I use them way too often.

I have noticed that, too, but I think it is because I am constantly creating test repos to debug git. Regular users don't have the same problem. :)

-Peff