Re: git push (mis ?)behavior

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 3, 2007, 16:44 UTC
Message-ID: <Pine.LNX.4.64.0710031742400.28395@racer.site>
In-Reply-To: <20071003162816.GA17403@artemis.corp>

Hi,

On Wed, 3 Oct 2007, Pierre Habouzit wrote:

Show 9 quoted lines

> On Wed, Oct 03, 2007 at 04:18:56PM +0000, Johannes Schindelin wrote:
> > This thread is getting painful.  Lot's of "I want"s, but nobody to date 
> > came up with a solution that makes both oldtimers and newtimers happy.
> 
> I think I made a proposal that tries to reach some kind of consensus:
> 
> `git push`::
>     no arguments given just pushes the current branch you're on, into
>     origin, if a refspec matches.

I use that sometimes, and I do not want only the current branch to be pushed.

> `git push <remote>`::
>     works like now (aka pushes all branches that match a remote branch
>     in the given remote).

That would make things inconsistent, and inconsistent things are always hard to explain.

Show 5 quoted lines

> This way, you can have current "git push" using "git push origin", but 
> you also have a convenient way to push only the current branch into your 
> default remote repository without needing to spell out:
> 
>   $ git push origin `git symbolic-ref HEAD`

I wonder how hard it would be to teach _everybody_ to specify _exactly_ what they want.

Of course, we'd need an "--existing" option to git-push to trigger the behaviour that we have right now.

Ciao, Dscho