Re: Minor annoyance with git push

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 9, 2008, 13:10 UTC
Message-ID: <alpine.LSU.1.00.0802091307160.11591@racer.site>
In-Reply-To: <6B804F0D-9C3B-46F3-B922-7A5CBEF55522@zib.de>

Hi,

On Sat, 9 Feb 2008, Steffen Prohaska wrote:

Show 14 quoted lines

> Personally, I decided it is safer to teach users to explicitly type what 
> they mean.  I'd probably not use the push.onlyHEAD config option.
> 
> I also proposed that the default could do nothing if no explicit push 
> lines are in the configuration file.  Users would be forced to 
> explicitly type what the want: Either they can say "--matching" or they 
> can say "--current".  This is similar to the new "git clean" default.  
> But I remember there *was* objection against this because everyone would 
> be forced to type more and different than "git clean" the default of 
> "git push" is considered "safe", so there's no need to protect the user 
> from "git push".
> 
> Junio proposed various possible changes to the configuration variables 
> that could resolve the issues.  I do not remember the details.

The way would be like this, I think:

- introduce a command line option for push, like "--push-common-refs", and 
issue a warning whenever "git push" is called without command line 
options (along the lines "This default behaviour is deprecated; please use 
--push-common-refs").

- in a waaaay later version, just take away the default action of "git 
push", instead showing the usage.

We had something similar wit the -i and -o options to "git commit".

Ciao, Dscho