Re: Minor annoyance with git push

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 10, 2008, 16:29 UTC
Message-ID: <alpine.LSU.1.00.0802101626201.11591@racer.site>
In-Reply-To: <20080210150216.GB8797@dervierte>

Hi,

On Sun, 10 Feb 2008, Steven Walter wrote:

Show 6 quoted lines

> I propose a new configuration option, remote.*.pushAllRefs, defaulting 
> to off.  When pushAllRefs is false, "git push" pushes only the current 
> branch.  When pushAllRefs is true, "git push" does what it does today. 
> For the old-timers, the impact of such a change seems minimal. 
> Worst-case, they run "git push," it doesn't do what they expect, they 
> run "git push origin" and then go change their config files.

I don't like it.

This would mean that I would have to look into the config everytime before I push, to be sure what semantics the push has in _this_ repository.

_If_ we change git-push's default behaviour, we have to introduce an option to do what the default action is now, _first_!

And _then_ we can start discussing what the default action should be, and I tend to think that it would make sense to default to the synopsis.

But that comes _second_, and we'd have to agree on _one_ course of action.

I mean, if you do not like the default behaviour of git-push now, you can always introduce an alias, if you want repository/host-specific actions.

Ciao, Dscho