threads / patch / 44337

patchdoc: remove reference to the traditional layout in git-tag.txt

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

## tl;dr

2 messages between Oct 20, 2016 and Oct 20, 2016. Diffs are folded; open one to read it.

replies: 1people: 2as markdown or json

Younes Khoudli· Oct 20, 2016, 13:21 UTC · lore

This is the only place in the documentation that the traditional layout is mentioned, and it is confusing. Remove it.

* 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(-)

Show changes to Documentation/git-tag.txt +2 −3

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

-- 
2.10.0

Junio C Hamano· Oct 20, 2016, 15:34 UTC · re: Younes Khoudli · lore

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

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