git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] fetch, pull doc: correct description of '--set-upstream'

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 13, 2020, 18:20 UTC
Message-ID
<xmqqimdm2yr9.fsf@gitster.c.googlers.com>
In-Reply-To
<pull.701.git.1597276320563.gitgitgadget@gmail.com>
"Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 9 quoted lines
> --- 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
Previous: Philippe Blain via GitGitGadget
Message 2 of 2 in “fetch, pull doc: correct description of '--set-upstream'”
  1. fetch, pull doc: correct description of '--set-upstream'Philippe Blain via GitGitGadget, Aug 12, 2020
  2. Junio C HamanoAug 13, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.