Thread (1 message) 1 message, 1 author, 2018-11-14

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

From: Junio C Hamano <hidden>
Date: 2018-11-14 08:16:21

Matthieu Moy [off-list ref] writes:
"Junio C Hamano" [off-list ref] wrote:
quoted
quoted
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.
[...]
quoted
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.
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help