From: Junio C Hamano <gitster@pobox.com>
To: muzimuzhi Z <muzimuzhi@gmail.com>, Clemens Buchacher <drizzd@aon.at>
Cc: git@vger.kernel.org
Subject: Re: Did config `branch.<name>.fetch` ever exist?
Date: Sun, 08 Jan 2023 13:35:50 +0900 [thread overview]
Message-ID: <xmqqfsclzlqx.fsf@gitster.g> (raw)
In-Reply-To: <CAEg0tHSLyaewkgGs0dEXfwQhKmbiO65bXZVU8t7Kn4WwJ1p0Fw@mail.gmail.com> (muzimuzhi Z.'s message of "Sun, 8 Jan 2023 01:34:09 +0800")
muzimuzhi Z <muzimuzhi@gmail.com> writes:
> Git configuration `branch.<name>.fetch` is mentioned in the first
> `git-fetch` example [1]:
>
>> - Update the remote-tracking branches:
>> $ 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.
>
> But I can't find its doc in `git-config`'s doc. Did
> `branch.<name>.fetch` ever exist?
>
> Searching in `git-config`'s doc for configs starting with `branch.` or
> ending with `.fetch`, it seems `branch.<name>.fetch` is a typo of
> `remote.<name>.fetch`.
Correct. Care to send a patch to correct it?
Thanks.
next prev parent reply other threads:[~2023-01-08 4:36 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 [this message]
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
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=xmqqfsclzlqx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=drizzd@aon.at \
--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).