Re: [PATCH] push: change needlessly ambiguous example in error

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 14, 2018, 08:16 UTC
Message-ID: <xmqqsh04m5v3.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <850526490.3010891.1542177378884.JavaMail.zimbra@matthieu-moy.fr>

Matthieu Moy <git@matthieu-moy.fr> writes:

Show 20 quoted lines

> "Junio C Hamano" <gitster@pobox.com> wrote:
>
>> > Where 'topic' is a tracking branch of 'origin/master' (I use
>> > push.default=upstream). I only recently discovered that I could push to
>> > 'HEAD" to do the same thing. So one ulterior motive is to make that more
>> > prominent.
> [...]
>> Do we consider the current behaviour useful? Is it documented
>
> Yes, since 1750783 (Documentation: more git push examples, 2009-01-26).
>
> It may be an accident that the doc says "to the same name on the
> remote." since it predates the introduction of push.default, but it
> does say so and it's the actual behavior.
>
>> already and widely known?
>
> https://stackoverflow.com/questions/14031970/git-push-current-branch-shortcut
>
> 458 votes for the answer suggesting it.

OK, that probably is good enough reason to keep the current behaviour and convince ourselves that there is nothing that needs to be done further on this topic.

Thanks.