From: kristofferhaugsbakk@fastmail.com
To: git@vger.kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
Karthik Nayak <karthik.188@gmail.com>,
Patrick Steinhardt <ps@pks.im>
Subject: [PATCH v2 0/2] doc: refs: put ref migration warning under the command
Date: Wed, 5 Aug 2026 21:02:34 +0200 [thread overview]
Message-ID: <V2_CV_git_ref_migration_warning.b20@msgid.xyz> (raw)
In-Reply-To: <CV_git_ref_migration_warning.b09@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Topic name (applied): doc-refs-migrate-limitations
Topic summary: Put ref migration warning as an admonition under the command
so that it is visible.
That’s the first patch. The second patch adds a missing `linkgit` since it
touches that same warning text.
I have two other patches that are not included here. They are unrelated
cleanups that I will post later. Here are the commit subjects and the first
paragraph so that you can see what they are about:
• doc: refs: wrap standalone placeholders in underscores
This is a synopsis manpage which means that standalone placeholders[1]
are supposed to use underscores (_), not backticks (`).[2]
• doc: refs: use inline-verbatim throughout
Use inline-verbatim backticks (`) for literal commands, options, and
subcommands listed under the “Commands” section.
§ Cc list
The two people that I have the impression that have worked most on
this command.
§ Changes in v2
• Patch 1/2: Use Warning admonition instead of Caution
• Patch 2/2: Add Ack
§ Link to v1
https://lore.kernel.org/git/CV_git_ref_migration_warning.b09@msgid.xyz/
[1/2] doc: refs: put ref migration warning under the command
[2/2] doc: refs: linkgit to git-maintenance(1)
Documentation/git-refs.adoc | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
Interdiff against v1:
diff --git a/Documentation/git-refs.adoc b/Documentation/git-refs.adoc
index 1ec26be0b4f..9063892651e 100644
--- a/Documentation/git-refs.adoc
+++ b/Documentation/git-refs.adoc
@@ -36,7 +36,7 @@ COMMANDS
`migrate`::
Migrate ref store between different formats.
+
-[CAUTION]
+[WARNING]
--
The ref format migration has several known limitations in its current form:
Range-diff against v1:
1: cc4d9ca5006 ! 1: 8a6415e2d9b doc: refs: put ref migration warning under the command
@@ Commit message
`migrate` description in order to see the “known limitations” for
it. This is important information since the text says that concurrent
writes can lead to an inconsistent migrated state. Let’s move that text
- up to the command description and put it inside a Caution admonition.
+ up to the command description and put it inside a Warning admonition.
This section made sense when it was added in 25a0023f (builtin/refs:
new command to migrate ref storage formats, 2024-06-06); `migrate` was
@@ Documentation/git-refs.adoc: COMMANDS
`migrate`::
Migrate ref store between different formats.
++
-+[CAUTION]
++[WARNING]
+--
+The ref format migration has several known limitations in its current form:
+
2: 7265de45c9d ! 2: 801a3d7f539 doc: refs: linkgit to git-maintenance(1)
@@ Metadata
## Commit message ##
doc: refs: linkgit to git-maintenance(1)
+ Acked-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
## Documentation/git-refs.adoc ##
base-commit: 13c7afec212fc97ce257d15601659314c6673d6c
--
2.54.0.22.g9e26862b904
next prev parent reply other threads:[~2026-08-05 19:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 9:07 [PATCH 0/2] doc: refs: put ref migration warning under the command kristofferhaugsbakk
2026-07-31 9:07 ` [PATCH 1/2] " kristofferhaugsbakk
2026-08-04 14:30 ` Patrick Steinhardt
2026-08-04 19:09 ` Kristoffer Haugsbakk
2026-08-05 8:07 ` Patrick Steinhardt
2026-08-05 9:13 ` Kristoffer Haugsbakk
2026-07-31 9:07 ` [PATCH 2/2] doc: refs: linkgit to git-maintenance(1) kristofferhaugsbakk
2026-08-04 14:30 ` Patrick Steinhardt
2026-07-31 16:39 ` [PATCH 0/2] doc: refs: put ref migration warning under the command Junio C Hamano
2026-08-04 14:30 ` Patrick Steinhardt
2026-08-05 19:02 ` kristofferhaugsbakk [this message]
2026-08-05 19:02 ` [PATCH v2 1/2] " kristofferhaugsbakk
2026-08-05 19:02 ` [PATCH v2 2/2] doc: refs: linkgit to git-maintenance(1) kristofferhaugsbakk
2026-08-06 5:15 ` [PATCH v2 0/2] doc: refs: put ref migration warning under the command Patrick Steinhardt
2026-08-06 17:32 ` Junio C Hamano
2026-08-06 6:20 ` [PATCH v3 " kristofferhaugsbakk
2026-08-06 6:20 ` [PATCH v3 1/2] " kristofferhaugsbakk
2026-08-06 6:20 ` [PATCH v3 2/2] doc: refs: linkgit to git-maintenance(1) kristofferhaugsbakk
2026-08-06 11:01 ` [PATCH v3 0/2] doc: refs: put ref migration warning under the command Karthik Nayak
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=V2_CV_git_ref_migration_warning.b20@msgid.xyz \
--to=kristofferhaugsbakk@fastmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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