From: "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Bence Ferdinandy <bence@ferdinandy.com>,
Philippe Blain <levraiphilippeblain@gmail.com>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: [PATCH 2/2] config/remote.txt: improve wording for 'remote.<name>.followRemoteHEAD'
Date: Fri, 14 Feb 2025 17:36:18 +0000 [thread overview]
Message-ID: <140794b8846e94ec3ff77920f0153f65d434f07e.1739554578.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1894.git.git.1739554578.gitgitgadget@gmail.com>
From: Philippe Blain <levraiphilippeblain@gmail.com>
Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
---
Documentation/config/remote.txt | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/config/remote.txt b/Documentation/config/remote.txt
index 1b9814e8aa4..25fe219d103 100644
--- a/Documentation/config/remote.txt
+++ b/Documentation/config/remote.txt
@@ -110,12 +110,12 @@ the values inherited from a lower priority configuration files (e.g.
remote.<name>.followRemoteHEAD::
How linkgit:git-fetch[1] should handle updates to `remotes/<name>/HEAD`.
The default value is "create", which will create `remotes/<name>/HEAD`
- if it exists on the remote, but not locally, but will not touch an
- already existing local reference. Setting to "warn" will print
- a message if the remote has a different value, than the local one and
+ if it exists on the remote, but not locally; this will not touch an
+ already existing local reference. Setting it to "warn" will print
+ a message if the remote has a different value than the local one;
in case there is no local reference, it behaves like "create".
A variant on "warn" is "warn-if-not-$branch", which behaves like
"warn", but if `HEAD` on the remote is `$branch` it will be silent.
- Setting to "always" will silently update it to the value on the remote.
- Finally, setting it to "never" will never change or create the local
- reference.
+ Setting it to "always" will silently update `remotes/<name>/HEAD` to
+ the value on the remote. Finally, setting it to "never" will never
+ change or create the local reference.
--
gitgitgadget
next prev parent reply other threads:[~2025-02-14 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 17:36 [PATCH 0/2] Documentation: fixups following followRemoteHEAD Philippe Blain via GitGitGadget
2025-02-14 17:36 ` [PATCH 1/2] config/remote.txt: reunite 'severOption' description paragraphs Philippe Blain via GitGitGadget
2025-02-14 22:01 ` Bence Ferdinandy
2025-02-14 22:11 ` Junio C Hamano
2025-02-14 17:36 ` Philippe Blain via GitGitGadget [this message]
2025-02-14 22:05 ` [PATCH 2/2] config/remote.txt: improve wording for 'remote.<name>.followRemoteHEAD' Bence Ferdinandy
2025-02-25 2:58 ` Philippe Blain
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=140794b8846e94ec3ff77920f0153f65d434f07e.1739554578.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=bence@ferdinandy.com \
--cc=git@vger.kernel.org \
--cc=levraiphilippeblain@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).