git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v3 2/2] doc: refs: linkgit to git-maintenance(1)

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Aug 6, 2026, 06:20 UTC
Message-ID
<V3_linkgit_maintenance.b25@msgid.xyz>
In-Reply-To
<V3_CV_git_ref_migration_warning.b23@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Acked-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Notes (series):
    v2: add Ack from previous round
 Documentation/git-refs.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-refs.adoc b/Documentation/git-refs.adoc
index 3b5af936ed6..9063892651e 100644
--- a/Documentation/git-refs.adoc
+++ b/Documentation/git-refs.adoc
@@ -46,7 +46,7 @@ The ref format migration has several known limitations in its current form:
   ongoing migration. Concurrent writes can lead to an inconsistent migrated
   state. Users are expected to block writes on a higher level. If your
   repository is registered for scheduled maintenance, it is recommended to
-  unregister it first with git-maintenance(1).
+  unregister it first with linkgit:git-maintenance[1].
 
 These limitations may eventually be lifted.
 --
-- 
2.54.0.22.g9e26862b904
Previous: kristofferhaugsbakk@fastmail.comNext: Karthik Nayak
Message 18 of 19 in “doc: refs: put ref migration warning under the command”
  1. 0/2 doc: refs: put ref migration warning under the commandkristofferhaugsbakk@fastmail.com, Jul 31, 2026
  2. 1/2 doc: refs: put ref migration warning under the commandkristofferhaugsbakk@fastmail.com, Jul 31, 2026
  3. Patrick SteinhardtAug 4, 2026
  4. Kristoffer HaugsbakkAug 4, 2026
  5. Patrick SteinhardtAug 5, 2026
  6. Kristoffer HaugsbakkAug 5, 2026
  7. 2/2 doc: refs: linkgit to git-maintenance(1)kristofferhaugsbakk@fastmail.com, Jul 31, 2026
  8. Patrick SteinhardtAug 4, 2026
  9. Junio C HamanoJul 31, 2026
  10. Patrick SteinhardtAug 4, 2026
  11. 0/2 doc: refs: put ref migration warning under the commandkristofferhaugsbakk@fastmail.com, Aug 5, 2026
  12. 1/2 doc: refs: put ref migration warning under the commandkristofferhaugsbakk@fastmail.com, Aug 5, 2026
  13. 2/2 doc: refs: linkgit to git-maintenance(1)kristofferhaugsbakk@fastmail.com, Aug 5, 2026
  14. Patrick SteinhardtAug 6, 2026
  15. Junio C HamanoAug 6, 2026
  16. 0/2 doc: refs: put ref migration warning under the commandkristofferhaugsbakk@fastmail.com, Aug 6, 2026
  17. 1/2 doc: refs: put ref migration warning under the commandkristofferhaugsbakk@fastmail.com, Aug 6, 2026
  18. 2/2 doc: refs: linkgit to git-maintenance(1)kristofferhaugsbakk@fastmail.com, Aug 6, 2026
  19. Karthik NayakAug 6, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.