From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
Git <git@vger.kernel.org>, "Johan Herland" <johan@herland.net>,
"Ramkumar Ramachandra" <artagnon@gmail.com>
Subject: Re: [PATCH] push: Re-include "push.default=tracking" in the documentation
Date: Thu, 06 Oct 2016 11:24:46 -0700 [thread overview]
Message-ID: <xmqqint5l4i9.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <vpqlgy1h28g.fsf@anie.imag.fr> (Matthieu Moy's message of "Thu, 06 Oct 2016 18:27:27 +0200")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> Junio, looks like from the 2013 discussion that you preferred just
>> having that mention in parenthesis instead of its own item, how about
>> just re-applying your fa23348 (with conflicts resolved)?
>
> (fa23348 did this:
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -1749,7 +1749,8 @@ push.default::
> +
> This is currently the default, but Git 2.0 will change the default
> to `simple`.
> -* `upstream` - push the current branch to its upstream branch.
> +* `upstream` - push the current branch to its upstream branch
> + (`tracking` is a deprecated synonym for this).
> )
>
> I agree that doing the same thing is the best option.
Sorry, I wasn't paying attention to this thread.
It seems that 87a70e4ce8 ("config doc: rewrite push.default
section", 2013-06-19) removed that mention by accident? The log
message of the commit does not say it actively wanted to remove
mention of `tracking` and/or why it wanted to do so, so I agree that
resurrecting that parenthetical mention is the easiest course of
action at this point.
However.
With today's description of push.default choices, each of which is a
full fledged paragraph, I no longer have the objection I had in
https://public-inbox.org/git/7vip6dgmx2.fsf@alter.siamese.dyndns.org/
against having `tracking` as a separate bullet item. If we add
* `tracking` - a deprecated synonym for `upstream`; do not use this.
to today's list, it would stand out as something different from
others and it will not cause the confusion I feared in the
discussion we had in early 2013. As Jonathan Nieder argued in the
thread back then, having it as one of the bullet point would help
people locate it without using "search" \C-s or / feature.
next prev parent reply other threads:[~2016-10-06 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 8:49 [PATCH] push: Re-include "push.default=tracking" in the documentation Ævar Arnfjörð Bjarmason
2016-10-06 9:13 ` Johan Herland
2016-10-06 12:13 ` Matthieu Moy
2016-10-06 16:18 ` Ævar Arnfjörð Bjarmason
2016-10-06 16:27 ` Matthieu Moy
2016-10-06 18:24 ` Junio C Hamano [this message]
2017-03-19 14:36 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2017-03-20 18:01 ` Junio C Hamano
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=xmqqint5l4i9.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=artagnon@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
/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).