dashed commands, was Re: disallowing push to currently checked-out branch

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 16, 2009, 10:50 UTC
Message-ID: <alpine.DEB.1.00.0902161147390.10279@pacific.mpi-cbg.de>
In-Reply-To: <alpine.DEB.1.10.0902152143430.14911@asgard.lang.hm>

Hi,

On Sun, 15 Feb 2009, david@lang.hm wrote:

Show 7 quoted lines

> I am not interested in forking git. but I am saying that a backwards 
> incompatible change had better _really_ be worth it, and not just be 
> worth it for the people who live an breath git, but for the users as 
> well (this is a test that the dashed name elimination failed. in spite 
> of a volcal few saying that all the commands in the path were causing 
> problems, most people couldn't understand why the git people wanted to 
> remove them)

Nope. It was not just because we could. It was an explicit request by more than one person that we do not put 110+ commands into /usr/bin/.

As for your argument that it should be worth for the users: if you are really thinking about the users, and not just yourself, you will see that the receive.denyCurrentBranch change is required.

BTW there is a timeline. Junio said already that it will be in 1.7 and not earlier.

Ciao, Dscho