Re: [PATCH 2/2] git-init: set receive.guardCurrentBranch = true for non-bare repositories

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 24, 2008, 11:00 UTC
Message-ID: <alpine.LSU.1.00.0803241158301.4353@racer.site>
In-Reply-To: <7v4pax3r6l.fsf@gitster.siamese.dyndns.org>

Hi,

On Sun, 23 Mar 2008, Junio C Hamano wrote:

Show 11 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > When initializing a non-bare repositories, you most likely want to 
> > avoid pushing into the current branch (because a push does not touch 
> > the working tree at all).
> 
> As I described in my other message, I suspect that treating the current 
> branch specially like this is a wrong approach.  The configuration might 
> be a good idea, but shouldn't it prevent any local branch from getting 
> updated?  Push into non-bare repository is simply a fetch run in reverse 
> direction.

That would break this work flow:

	# machine A
	$ git push B master:refs/heads/tmp

	# machine B
	$ git merge tmp
	$ git branch -d tmp

Besides, there is a _vital_ difference between the current branch, and any other local branch: pushing into other local branches cannot make your working tree stale.

Ciao, Dscho