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 0/2] doc: refs: put ref migration warning under the command
Date: Fri, 31 Jul 2026 11:07:01 +0200 [thread overview]
Message-ID: <CV_git_ref_migration_warning.b09@msgid.xyz> (raw)
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Topic name: 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.
[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(-)
base-commit: 13c7afec212fc97ce257d15601659314c6673d6c
--
2.54.0.22.g9e26862b904
next reply other threads:[~2026-07-31 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 9:07 kristofferhaugsbakk [this message]
2026-07-31 9:07 ` [PATCH 1/2] doc: refs: put ref migration warning under the command kristofferhaugsbakk
2026-07-31 9:07 ` [PATCH 2/2] doc: refs: linkgit to git-maintenance(1) kristofferhaugsbakk
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=CV_git_ref_migration_warning.b09@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.