git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <git@matthieu-moy.fr>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] push: change needlessly ambiguous example in error
Date: Wed, 14 Nov 2018 17:16:16 +0900	[thread overview]
Message-ID: <xmqqsh04m5v3.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <850526490.3010891.1542177378884.JavaMail.zimbra@matthieu-moy.fr> (Matthieu Moy's message of "Wed, 14 Nov 2018 07:36:18 +0100 (CET)")

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

> "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.

      reply	other threads:[~2018-11-14  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 20:39 [PATCH] push: change needlessly ambiguous example in error Ævar Arnfjörð Bjarmason
2018-11-13 21:37 ` Matthieu Moy
2018-11-13 21:55   ` Ævar Arnfjörð Bjarmason
2018-11-14  4:32     ` Junio C Hamano
2018-11-14  6:36       ` Matthieu Moy
2018-11-14  8:16         ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqsh04m5v3.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@matthieu-moy.fr \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).