From: Junio C Hamano <gitster@pobox.com>
To: muzimuzhi Z <muzimuzhi@gmail.com>
Cc: Clemens Buchacher <drizzd@gmx.net>, git@vger.kernel.org
Subject: Re: [PATCH v2] doc: fix non-existent config name
Date: Fri, 13 Jan 2023 17:33:00 -0800 [thread overview]
Message-ID: <xmqqedrxoq7n.fsf@gitster.g> (raw)
In-Reply-To: <CAEg0tHSZi22RUBREJB=Cfy6O72cicv9FTkgo_Z=gvGRdPK1acw@mail.gmail.com> (muzimuzhi Z.'s message of "Sat, 14 Jan 2023 09:12:12 +0800")
muzimuzhi Z <muzimuzhi@gmail.com> writes:
> From c879cb10f61afc361c484267f498d5815bc1b932 Mon Sep 17 00:00:00 2001
> From: muzimuzhi <muzimuzhi@gmail.com>
The "author identity" is taken from this line (or from the e-mail
header), and it should be identical to your sign-off.
> Date: Mon, 9 Jan 2023 06:37:47 +0800
> Subject: [PATCH v2] doc: fix non-existent config name
In general, there shouldn't be a reason to include the above four
lines in your message body. An exception is "From:" to override the
author identity when you cannot send your e-mail using the same name
as what is used on your sign-off. See Discussion section of "git am"
manual page.
> Replace non-existent `branch.<name>.fetch` to `remote.<repository>.fetch`, in
> the first example in `git-fetch` doc, which was introduced in
> d504f6975d (modernize fetch/merge/pull examples, 2009-10-21).
>
> Rename placeholder `<name>` to `<repository>`, to be consistent with all other
> uses in git docs, except that `git-config.txt` uses `remote.<name>.fetch` in
> its "Variables" section.
>
> Also add missing monospace markups.
>
> Signed-off-by: Yukai Chou <muzimuzhi@gmail.com>
Perfect. Will queue.
> Changes compared to PATCH v1:
> - Update commit reference in a non-shallow clone, resulting in longer
> <abbrev-hash>
Great.
> diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt
> index 63d9569e16..fba66f1460 100644
> --- a/Documentation/git-fetch.txt
> +++ b/Documentation/git-fetch.txt
> @@ -251,10 +251,10 @@ EXAMPLES
> $ git fetch origin
> ------------------------------------------------
> +
> -The above command copies all branches from the remote refs/heads/
> -namespace and stores them to the local refs/remotes/origin/ namespace,
> -unless the branch.<name>.fetch option is used to specify a non-default
> -refspec.
> +The above command copies all branches from the remote `refs/heads/`
> +namespace and stores them to the local `refs/remotes/origin/` namespace,
> +unless the `remote.<repository>.fetch` option is used to specify a
> +non-default refspec.
>
> * Using refspecs explicitly:
> +
prev parent reply other threads:[~2023-01-14 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 17:34 Did config `branch.<name>.fetch` ever exist? muzimuzhi Z
2023-01-08 4:35 ` Junio C Hamano
2023-01-09 4:18 ` [PATCH] doc: fix non-existing config name muzimuzhi Z
2023-01-09 21:38 ` muzimuzhi Z
2023-01-13 17:54 ` Junio C Hamano
2023-01-14 1:12 ` [PATCH v2] doc: fix non-existent " muzimuzhi Z
2023-01-14 1:33 ` 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=xmqqedrxoq7n.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=drizzd@gmx.net \
--cc=git@vger.kernel.org \
--cc=muzimuzhi@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;
as well as URLs for NNTP newsgroup(s).