{"thread":{"id":"59044","subject":"Did config `branch..fetch` ever exist?","startedAt":"2023-01-07T17:34:28Z","lastAt":"2023-01-14T01:33:07Z","messageCount":7,"participants":["muzimuzhi Z","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"469883","messageId":"CAEg0tHSLyaewkgGs0dEXfwQhKmbiO65bXZVU8t7Kn4WwJ1p0Fw@mail.gmail.com","threadId":"59044","inReplyTo":null,"subject":"Did config `branch..fetch` ever exist?","fromName":"muzimuzhi Z","fromEmail":"muzimuzhi@gmail.com","sentAt":"2023-01-07T17:34:09Z","receivedAt":"2023-01-07T17:34:28Z","isPatch":false,"sender":{"key":"muzimuzhi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6376638?v=4"},"body":"Hi all,\n\n(originally posted on stackoverflow: https://stackoverflow.com/q/75040372)\n\nGit configuration `branch..fetch` is mentioned in the first\n`git-fetch` example [1]:\n\n> - Update the remote-tracking branches:\n> $ git fetch origin\n> 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..fetch option is used to specify a non-default refspec.\n\nBut I can't find its doc in `git-config`'s doc. Did\n`branch..fetch` ever exist?\n\nSearching in `git-config`'s doc for configs starting with `branch.` or\nending with `.fetch`, it seems `branch..fetch` is a typo of\n`remote..fetch`.\n\nPS: That `git-fetch` example was added in commit d504f69 in 2009. [3]\n\n[1] https://git-scm.com/docs/git-fetch#_examples\n[2] https://git-scm.com/docs/git-config\n[3] https://github.com/git/git/commit/d504f6975d34025ed3b5478b657789410b52cdb1\n\nbest regards,\nYukai Chou\n"},{"id":"469902","messageId":"xmqqfsclzlqx.fsf@gitster.g","threadId":"59044","inReplyTo":"CAEg0tHSLyaewkgGs0dEXfwQhKmbiO65bXZVU8t7Kn4WwJ1p0Fw@mail.gmail.com","subject":"Re: Did config `branch..fetch` ever exist?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-01-08T04:35:50Z","receivedAt":"2023-01-08T04:36:03Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"muzimuzhi Z writes:\n\n> Git configuration `branch..fetch` is mentioned in the first\n> `git-fetch` example [1]:\n>\n>> - Update the remote-tracking branches:\n>> $ git fetch origin\n>> The above command copies all branches from the remote\n>> refs/heads/ namespace and stores them to the local\n>> refs/remotes/origin/ namespace, unless the branch..fetch\n>> option is used to specify a non-default refspec.\n>\n> But I can't find its doc in `git-config`'s doc. Did\n> `branch..fetch` ever exist?\n>\n> Searching in `git-config`'s doc for configs starting with `branch.` or\n> ending with `.fetch`, it seems `branch..fetch` is a typo of\n> `remote..fetch`.\n\nCorrect. Care to send a patch to correct it?\n\nThanks.\n\n"},{"id":"469936","messageId":"CAEg0tHT5PD4K89E3fcNq_WbaLPHozLi-PsJFDsQrzkGi7Na9jg@mail.gmail.com","threadId":"59044","inReplyTo":"xmqqfsclzlqx.fsf@gitster.g","subject":"[PATCH] doc: fix non-existing config name","fromName":"muzimuzhi Z","fromEmail":"muzimuzhi@gmail.com","sentAt":"2023-01-09T04:18:34Z","receivedAt":"2023-01-09T04:33:21Z","isPatch":true,"sender":{"key":"muzimuzhi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6376638?v=4"},"body":"Replace non-existent `branch..fetch` to `remote..fetch`, in\nthe first example in `git-fetch` doc, which was introduced in\nd504f69 (modernize fetch/merge/pull examples, 2009-10-21).\n\nRename placeholder `` to ``, to be consistent with all other\nuses in git docs, except that `git-config.txt` uses `remote..fetch` in\nits \"Variables\" section.\n\nAlso add missing monospace markups.\n\nSigned-off-by: muzimuzhi \n---\n Documentation/git-fetch.txt | 8 ++++----\n 1 file changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt\nindex 63d9569..fba66f1 100644\n--- a/Documentation/git-fetch.txt\n+++ b/Documentation/git-fetch.txt\n@@ -251,10 +251,10 @@ EXAMPLES\n $ git fetch origin\n ------------------------------------------------\n +\n-The above command copies all branches from the remote refs/heads/\n-namespace and stores them to the local refs/remotes/origin/ namespace,\n-unless the branch..fetch option is used to specify a non-default\n-refspec.\n+The above command copies all branches from the remote `refs/heads/`\n+namespace and stores them to the local `refs/remotes/origin/` namespace,\n+unless the `remote..fetch` option is used to specify a\n+non-default refspec.\n\n * Using refspecs explicitly:\n +\n-- \n2.39.0\n"},{"id":"470013","messageId":"CAEg0tHQtf9G0N24Xfe-gvRM1AFaiS_ApcuQ8hZtsZAeMhhVWAQ@mail.gmail.com","threadId":"59044","inReplyTo":"CAEg0tHT5PD4K89E3fcNq_WbaLPHozLi-PsJFDsQrzkGi7Na9jg@mail.gmail.com","subject":"Re: [PATCH] doc: fix non-existing config name","fromName":"muzimuzhi Z","fromEmail":"muzimuzhi@gmail.com","sentAt":"2023-01-09T21:38:59Z","receivedAt":"2023-01-09T21:41:41Z","isPatch":true,"sender":{"key":"muzimuzhi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6376638?v=4"},"body":"Somehow My last mail failed to sent to Clemens Buchacher (drizzd@aon.at):\n\n> 550 5.7.1 : Recipient address rejected: mailbox not found\n\nI found two lines about Clemens in `.mailmap` (see below) [1] and\ndrizzd@gmx.net was used last time when Clemens mailed to the current\nmailing list in Feb 2019 [2].\n\n Clemens Buchacher \n Clemens Buchacher \n\nThus I added drizzd@gmx.net to cc.\n\nyukai\n\n[1] https://github.com/git/git/blob/a38d39a4c50d1275833aba54c4dbdfce9e2e9ca1/.mailmap#L45-L46\n[2] https://lore.kernel.org/git/B168DCB1-7A69-4729-89C7-B513464DD468@gmx.net/\n\nmuzimuzhi Z 于2023年1月9日周一 12:18写道：\n>\n> Replace non-existent `branch..fetch` to `remote..fetch`, in\n> the first example in `git-fetch` doc, which was introduced in\n> d504f69 (modernize fetch/merge/pull examples, 2009-10-21).\n>\n> Rename placeholder `` to ``, to be consistent with all other\n> uses in git docs, except that `git-config.txt` uses `remote..fetch` in\n> its \"Variables\" section.\n>\n> Also add missing monospace markups.\n>\n> Signed-off-by: muzimuzhi \n> ---\n> Documentation/git-fetch.txt | 8 ++++----\n> 1 file changed, 4 insertions(+), 4 deletions(-)\n>\n> diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt\n> index 63d9569..fba66f1 100644\n> --- a/Documentation/git-fetch.txt\n> +++ b/Documentation/git-fetch.txt\n> @@ -251,10 +251,10 @@ EXAMPLES\n> $ git fetch origin\n> ------------------------------------------------\n> +\n> -The above command copies all branches from the remote refs/heads/\n> -namespace and stores them to the local refs/remotes/origin/ namespace,\n> -unless the branch..fetch option is used to specify a non-default\n> -refspec.\n> +The above command copies all branches from the remote `refs/heads/`\n> +namespace and stores them to the local `refs/remotes/origin/` namespace,\n> +unless the `remote..fetch` option is used to specify a\n> +non-default refspec.\n>\n> * Using refspecs explicitly:\n> +\n> --\n> 2.39.0\n"},{"id":"470293","messageId":"xmqqo7r248x9.fsf@gitster.g","threadId":"59044","inReplyTo":"CAEg0tHQtf9G0N24Xfe-gvRM1AFaiS_ApcuQ8hZtsZAeMhhVWAQ@mail.gmail.com","subject":"Re: [PATCH] doc: fix non-existing config name","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-01-13T17:54:26Z","receivedAt":"2023-01-13T18:01:23Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"muzimuzhi Z writes:\n\n> Somehow My last mail failed to sent to Clemens Buchacher (drizzd@aon.at):\n>\n>> 550 5.7.1 : Recipient address rejected: mailbox not found\n>\n> I found two lines about Clemens in `.mailmap` (see below) [1] and\n> drizzd@gmx.net was used last time when Clemens mailed to the current\n> mailing list in Feb 2019 [2].\n>\n> Clemens Buchacher \n> Clemens Buchacher \n>\n> Thus I added drizzd@gmx.net to cc.\n\nThanks for the above explanation.\n\n> yukai\n\nIs that your name, or is it \"muzimuzhi Z\"? Please see and follow\nDocumentation/SubmittingPatches:[[sign-off]] and [[real-name]]\nsections.\n\nThe patch, including the proposed log message, looks excellent.\n\nThanks.\n\n>> Replace non-existent `branch..fetch` to `remote..fetch`, in\n>> the first example in `git-fetch` doc, which was introduced in\n>> d504f69 (modernize fetch/merge/pull examples, 2009-10-21).\n>>\n>> Rename placeholder `` to ``, to be consistent with all other\n>> uses in git docs, except that `git-config.txt` uses `remote..fetch` in\n>> its \"Variables\" section.\n>>\n>> Also add missing monospace markups.\n>>\n>> Signed-off-by: muzimuzhi \n>> ---\n>> Documentation/git-fetch.txt | 8 ++++----\n>> 1 file changed, 4 insertions(+), 4 deletions(-)\n>>\n>> diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt\n>> index 63d9569..fba66f1 100644\n>> --- a/Documentation/git-fetch.txt\n>> +++ b/Documentation/git-fetch.txt\n>> @@ -251,10 +251,10 @@ EXAMPLES\n>> $ git fetch origin\n>> ------------------------------------------------\n>> +\n>> -The above command copies all branches from the remote refs/heads/\n>> -namespace and stores them to the local refs/remotes/origin/ namespace,\n>> -unless the branch..fetch option is used to specify a non-default\n>> -refspec.\n>> +The above command copies all branches from the remote `refs/heads/`\n>> +namespace and stores them to the local `refs/remotes/origin/` namespace,\n>> +unless the `remote..fetch` option is used to specify a\n>> +non-default refspec.\n>>\n>> * Using refspecs explicitly:\n>> +\n>> --\n>> 2.39.0\n"},{"id":"470315","messageId":"CAEg0tHSZi22RUBREJB=Cfy6O72cicv9FTkgo_Z=gvGRdPK1acw@mail.gmail.com","threadId":"59044","inReplyTo":"xmqqo7r248x9.fsf@gitster.g","subject":"[PATCH v2] doc: fix non-existent config name","fromName":"muzimuzhi Z","fromEmail":"muzimuzhi@gmail.com","sentAt":"2023-01-14T01:12:12Z","receivedAt":"2023-01-14T01:12:30Z","isPatch":true,"sender":{"key":"muzimuzhi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6376638?v=4"},"body":"From c879cb10f61afc361c484267f498d5815bc1b932 Mon Sep 17 00:00:00 2001\nFrom: muzimuzhi \nDate: Mon, 9 Jan 2023 06:37:47 +0800\nSubject: [PATCH v2] doc: fix non-existent config name\n\nReplace non-existent `branch..fetch` to `remote..fetch`, in\nthe first example in `git-fetch` doc, which was introduced in\nd504f6975d (modernize fetch/merge/pull examples, 2009-10-21).\n\nRename placeholder `` to ``, to be consistent with all other\nuses in git docs, except that `git-config.txt` uses `remote..fetch` in\nits \"Variables\" section.\n\nAlso add missing monospace markups.\n\nSigned-off-by: Yukai Chou \n---\n\nChanges compared to PATCH v1:\n - Use real name in sign-off\n - Update commit reference in a non-shallow clone, resulting in longer\n \n - Use word \"non-existent\" in commit message uniformly\n - Rebase to latest master a38d39a4c5 (The sixth batch, 2023-01-08)\n\n Documentation/git-fetch.txt | 8 ++++----\n 1 file changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt\nindex 63d9569e16..fba66f1460 100644\n--- a/Documentation/git-fetch.txt\n+++ b/Documentation/git-fetch.txt\n@@ -251,10 +251,10 @@ EXAMPLES\n $ git fetch origin\n ------------------------------------------------\n +\n-The above command copies all branches from the remote refs/heads/\n-namespace and stores them to the local refs/remotes/origin/ namespace,\n-unless the branch..fetch option is used to specify a non-default\n-refspec.\n+The above command copies all branches from the remote `refs/heads/`\n+namespace and stores them to the local `refs/remotes/origin/` namespace,\n+unless the `remote..fetch` option is used to specify a\n+non-default refspec.\n\n * Using refspecs explicitly:\n +\n-- \n2.39.0\n"},{"id":"470317","messageId":"xmqqedrxoq7n.fsf@gitster.g","threadId":"59044","inReplyTo":"CAEg0tHSZi22RUBREJB=Cfy6O72cicv9FTkgo_Z=gvGRdPK1acw@mail.gmail.com","subject":"Re: [PATCH v2] doc: fix non-existent config name","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-01-14T01:33:00Z","receivedAt":"2023-01-14T01:33:07Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"muzimuzhi Z writes:\n\n> From c879cb10f61afc361c484267f498d5815bc1b932 Mon Sep 17 00:00:00 2001\n> From: muzimuzhi \n\nThe \"author identity\" is taken from this line (or from the e-mail\nheader), and it should be identical to your sign-off.\n\n> Date: Mon, 9 Jan 2023 06:37:47 +0800\n> Subject: [PATCH v2] doc: fix non-existent config name\n\nIn general, there shouldn't be a reason to include the above four\nlines in your message body. An exception is \"From:\" to override the\nauthor identity when you cannot send your e-mail using the same name\nas what is used on your sign-off. See Discussion section of \"git am\"\nmanual page.\n\n> Replace non-existent `branch..fetch` to `remote..fetch`, in\n> the first example in `git-fetch` doc, which was introduced in\n> d504f6975d (modernize fetch/merge/pull examples, 2009-10-21).\n>\n> Rename placeholder `` to ``, to be consistent with all other\n> uses in git docs, except that `git-config.txt` uses `remote..fetch` in\n> its \"Variables\" section.\n>\n> Also add missing monospace markups.\n>\n> Signed-off-by: Yukai Chou \n\nPerfect. Will queue.\n\n> Changes compared to PATCH v1:\n\n> - Update commit reference in a non-shallow clone, resulting in longer\n> \n\nGreat.\n\n> diff --git a/Documentation/git-fetch.txt b/Documentation/git-fetch.txt\n> index 63d9569e16..fba66f1460 100644\n> --- a/Documentation/git-fetch.txt\n> +++ b/Documentation/git-fetch.txt\n> @@ -251,10 +251,10 @@ EXAMPLES\n> $ git fetch origin\n> ------------------------------------------------\n> +\n> -The above command copies all branches from the remote refs/heads/\n> -namespace and stores them to the local refs/remotes/origin/ namespace,\n> -unless the branch..fetch option is used to specify a non-default\n> -refspec.\n> +The above command copies all branches from the remote `refs/heads/`\n> +namespace and stores them to the local `refs/remotes/origin/` namespace,\n> +unless the `remote..fetch` option is used to specify a\n> +non-default refspec.\n>\n> * Using refspecs explicitly:\n> +\n"}]}