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

Re: [PATCH] doc: remove reference to the traditional layout in git-tag.txt

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 20, 2016, 15:34 UTC
Message-ID
<xmqqvawnhw52.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20161020132144.6018-1-younes.khoudli@gmail.com>
Younes Khoudli <younes.khoudli@gmail.com> writes:
> This is the only place in the documentation that the traditional layout
> is mentioned, and it is confusing. Remove it.

Yeah, the information is not incorrect per-se, but certainly is out of place and immaterial to what this part of the documentation tries to teach.

Will queue; thanks.
Show 24 quoted lines
>
> * Documentation/git-tag.txt: Here.
>
> Signed-off-by: Younes Khoudli <younes.khoudli@gmail.com>
> ---
>  Documentation/git-tag.txt | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
> index 7ecca8e..80019c5 100644
> --- a/Documentation/git-tag.txt
> +++ b/Documentation/git-tag.txt
> @@ -253,9 +253,8 @@ On Automatic following
>  ~~~~~~~~~~~~~~~~~~~~~~
>  
>  If you are following somebody else's tree, you are most likely
> -using remote-tracking branches (`refs/heads/origin` in traditional
> -layout, or `refs/remotes/origin/master` in the separate-remote
> -layout).  You usually want the tags from the other end.
> +using remote-tracking branches (eg. `refs/remotes/origin/master`).
> +You usually want the tags from the other end.
>  
>  On the other hand, if you are fetching because you would want a
>  one-shot merge from somebody else, you typically do not want to
Previous: Younes Khoudli
Message 2 of 2 in “doc: remove reference to the traditional layout in git-tag.txt”
  1. doc: remove reference to the traditional layout in git-tag.txtYounes Khoudli, Oct 20, 2016
  2. Junio C HamanoOct 20, 2016

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.