From: Junio C Hamano <gitster@pobox.com>
To: Younes Khoudli <younes.khoudli@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc: remove reference to the traditional layout in git-tag.txt
Date: Thu, 20 Oct 2016 08:34:33 -0700 [thread overview]
Message-ID: <xmqqvawnhw52.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20161020132144.6018-1-younes.khoudli@gmail.com> (Younes Khoudli's message of "Thu, 20 Oct 2016 15:21:44 +0200")
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.
>
> * 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
prev parent reply other threads:[~2016-10-20 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 13:21 [PATCH] doc: remove reference to the traditional layout in git-tag.txt Younes Khoudli
2016-10-20 15:34 ` 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=xmqqvawnhw52.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=younes.khoudli@gmail.com \
/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