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

Re: [PATCH v2 0/5] doc: move BreakingChanges to a manpage

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Oct 20, 2026, 13:53 UTC
Message-ID
<8160091f-6227-42f7-ac0d-d63e23babffa@app.fastmail.com>
In-Reply-To
<CALnO6CBuKKF=nCObFCK0coCDqbK=OJTWEshEtj6NaVV6XpWGuw@mail.gmail.com>
On Tue, Oct 20, 2026, at 15:48, D. Ben Knoble wrote:
Show 11 quoted lines
> On Tue, Oct 20, 2026 at 9:41 AM Kristoffer Haugsbakk
> <kristofferhaugsbakk@fastmail.com> wrote:
>> On Thu, Oct 8, 2026, at 21:27, kristofferhaugsbakk@fastmail.com wrote:
>> >[snip of a snip]
>>
>> Is there any interest in continuing this series?
>
> For myself, I favor making more of Git's documentation accessible to folks.
>
> I haven't reviewed the series, and I know there was some conversation
> on how to handle links, but I'm in favor of the direction.

Thanks. Yeah the link thing turned out to be the most work here. I can of course drop it if people don’t think it’s an improvement. Because as far as making the documentation more accessible, all the info is there with instructions on how to use the references. Just with an extra step.

Previous: D. Ben KnobleNext: Junio C Hamano
Message 28 of 35 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. Patrick SteinhardtSep 30, 2026
  4. Kristoffer HaugsbakkSep 30, 2026
  5. Patrick SteinhardtSep 30, 2026
  6. 2/4 doc: gitbreaking-changes: replace msg-ids with URLskristofferhaugsbakk@fastmail.com, Sep 28, 2026
  7. Patrick SteinhardtSep 30, 2026
  8. Kristoffer HaugsbakkSep 30, 2026
  9. Junio C HamanoSep 30, 2026
  10. Patrick SteinhardtOct 1, 2026
  11. Kristoffer HaugsbakkOct 3, 2026
  12. Kristoffer HaugsbakkOct 3, 2026
  13. Junio C HamanoOct 4, 2026
  14. Kristoffer HaugsbakkOct 6, 2026
  15. Junio C HamanoOct 6, 2026
  16. 3/4 doc: gitbreaking-changes: add note about living documentkristofferhaugsbakk@fastmail.com, Sep 28, 2026
  17. 4/4 doc: git: mention gitbreaking-changes(7)kristofferhaugsbakk@fastmail.com, Sep 28, 2026
  18. 0/5 doc: move BreakingChanges to a manpagekristofferhaugsbakk@fastmail.com, Oct 8, 2026
  19. 1/5 doc: BreakingChanges: transform to a manpagekristofferhaugsbakk@fastmail.com, Oct 8, 2026
  20. D. Ben KnobleOct 8, 2026
  21. Kristoffer HaugsbakkOct 9, 2026
  22. 2/5 doc: gitbreaking-changes: create from BreakingChangeskristofferhaugsbakk@fastmail.com, Oct 8, 2026
  23. 3/5 doc: gitbreaking-changes: replace msg-ids with URLskristofferhaugsbakk@fastmail.com, Oct 8, 2026
  24. 4/5 doc: gitbreaking-changes: add note about living documentkristofferhaugsbakk@fastmail.com, Oct 8, 2026
  25. 5/5 doc: gitbreaking-changes: move new-items discussion to the endkristofferhaugsbakk@fastmail.com, Oct 8, 2026
  26. Kristoffer HaugsbakkOct 20, 2026
  27. D. Ben KnobleOct 20, 2026
  28. Kristoffer HaugsbakkOct 20, 2026
  29. Junio C HamanoOct 21, 2026
  30. Kristoffer HaugsbakkOct 21, 2026
  31. Junio C HamanoOct 21, 2026
  32. Kristoffer HaugsbakkOct 22, 2026
  33. Junio C HamanoOct 22, 2026
  34. Kristoffer HaugsbakkNov 20, 2026
  35. Patrick SteinhardtOct 22, 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.