From: Junio C Hamano <gitster@pobox.com>
To: "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,
Corentin BOMPARD <corentin.bompard@etu.univ-lyon1.fr>,
Nathan BERBEZIER <nathan.berbezier@etu.univ-lyon1.fr>,
Pablo CHABANNE <pablo.chabanne@etu.univ-lyon1.fr>,
Matthieu Moy <git@matthieu-moy.fr>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH] fetch, pull doc: correct description of '--set-upstream'
Date: Thu, 13 Aug 2020 11:20:58 -0700 [thread overview]
Message-ID: <xmqqimdm2yr9.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <pull.701.git.1597276320563.gitgitgadget@gmail.com> (Philippe Blain via GitGitGadget's message of "Wed, 12 Aug 2020 23:52:00 +0000")
"Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com> writes:
> --- a/Documentation/fetch-options.txt
> +++ b/Documentation/fetch-options.txt
> @@ -186,7 +186,7 @@ ifndef::git-pull[]
> endif::git-pull[]
>
> --set-upstream::
> - If the remote is fetched successfully, pull and add upstream
> + If the remote is fetched successfully, add upstream
> (tracking) reference, used by argument-less
Makes sense. Will queue. Thanks.
> linkgit:git-pull[1] and other commands. For more information,
> see `branch.<name>.merge` and `branch.<name>.remote` in
>
> base-commit: 7814e8a05a59c0cf5fb186661d1551c75d1299b5
prev parent reply other threads:[~2020-08-13 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 23:52 [PATCH] fetch, pull doc: correct description of '--set-upstream' Philippe Blain via GitGitGadget
2020-08-13 18:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqimdm2yr9.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=corentin.bompard@etu.univ-lyon1.fr \
--cc=git@matthieu-moy.fr \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=levraiphilippeblain@gmail.com \
--cc=nathan.berbezier@etu.univ-lyon1.fr \
--cc=pablo.chabanne@etu.univ-lyon1.fr \
/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.
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 NNTP newsgroup(s).