git/list[1] front-page[2] threads[3] people[4] search[5] about
wed 2026-10-07 16:50 UTC

Re: [RFC PATCH 2/4] doc: gitbreaking-changes: replace msg-ids with URLs

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 6, 2026, 20:33 UTC
Message-ID
<xmqqjynud0wn.fsf@gitster.g>
In-Reply-To
<c85f5906-630b-4335-a7ae-09af665bb335@app.fastmail.com>
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
Show 10 quoted lines
> What if we used footnotes for all of the original msg-ids?
>
>     <URL>[1]
>
>     [...]
>
>     [1]: <msg-id>
>
> Or maybe just for the ones that need URL encoding? I personally think it
> would be better to use them for all if we go for this approach.

If this is an attempt to cater to those who prefer raw message IDs over URLs that encode them, I doubt it is an improvement.

A footnote placed far down the document that merely repeats what is already in the URL is uglier than simply using the URL without such a footnote layout. The cost of avoiding this ugliness is rather small for such users. They have to extract the encoded message ID from the URL, perhaps decoding it manually, before using it. That is not too much work.

So, unless we can use a clickable link whose text can be copied to get the raw message ID (which even novice users would clearly recognize as a link rather than an e-mail address), which we already agreed is impossible, let's just provide the URL. Users can copy and paste it into their browsers, and many terminal emulators will let them click it directly, as you mentioned earlier.

Thanks.
Previous: Kristoffer Haugsbakk
Message 17 of 17 in “doc: move BreakingChanges to a manpage”
  1. 0/4 doc: move BreakingChanges to a manpagekristofferhaugsbakk@fastmail.com, Sep 28, 2026
  2. 1/4 doc: transform breaking changes doc to a manpagekristofferhaugsbakk@fastmail.com, Sep 28, 2026
  3. 2/4 doc: gitbreaking-changes: replace msg-ids with URLskristofferhaugsbakk@fastmail.com, Sep 28, 2026
  4. 3/4 doc: gitbreaking-changes: add note about living documentkristofferhaugsbakk@fastmail.com, Sep 28, 2026
  5. 4/4 doc: git: mention gitbreaking-changes(7)kristofferhaugsbakk@fastmail.com, Sep 28, 2026
  6. Patrick SteinhardtSep 30, 2026
  7. Patrick SteinhardtSep 30, 2026
  8. Kristoffer HaugsbakkSep 30, 2026
  9. Kristoffer HaugsbakkSep 30, 2026
  10. Patrick SteinhardtSep 30, 2026
  11. Junio C HamanoSep 30, 2026
  12. Patrick SteinhardtOct 1, 2026
  13. Kristoffer HaugsbakkOct 3, 2026
  14. Kristoffer HaugsbakkOct 3, 2026
  15. Junio C HamanoOct 4, 2026
  16. Kristoffer HaugsbakkOct 6, 2026
  17. Junio C HamanoOct 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.