[PATCH v2] doc: fix non-existent config name
- From
muzimuzhi Z <muzimuzhi@gmail.com>
- Date
- Jan 14, 2023, 01:12 UTC
- Message-ID
- <CAEg0tHSZi22RUBREJB=Cfy6O72cicv9FTkgo_Z=gvGRdPK1acw@mail.gmail.com>
- In-Reply-To
- <xmqqo7r248x9.fsf@gitster.g>
From c879cb10f61afc361c484267f498d5815bc1b932 Mon Sep 17 00:00:00 2001 From: muzimuzhi <muzimuzhi@gmail.com> Date: Mon, 9 Jan 2023 06:37:47 +0800 Subject: [PATCH v2] doc: fix non-existent config name
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> ---
Changes compared to PATCH v1: - Use real name in sign-off - Update commit reference in a non-shallow clone, resulting in longer <abbrev-hash> - Use word "non-existent" in commit message uniformly - Rebase to latest master a38d39a4c5 (The sixth batch, 2023-01-08)
Documentation/git-fetch.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
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: +
-- 2.39.0