Kristoffer Haugsbakk's four-patch RFC converts the BreakingChanges document into a manpage, replaces message IDs with URLs, adds a note that it is a living document, and mentions it from git(1). His argument is that users are affected by breaking changes far more than developers who already follow the project's discussions, so advertising them to all users helps the community prepare.
Junio C Hamano said making the text available from 'git help' would be good, but asked what happens when Git 3.0 comes. He asked whether every section would be rewritten to say 'we used to do this differently before 3.0'. He also questioned whether keeping such a historical document is worth it, asking whether anyone still cares about the major issues in the 1.x to 2.0 transition. He said the rewriting effort itself is not his main concern.
Patrick Steinhardt argued for keeping it for a long time. Users often upgrade across several versions, for example between LTS releases, and may land on 3.x rather than 3.0 itself. They would still want to learn what changed, so he would keep it at least until all supported distributions have moved to 3.0.
Haugsbakk said he is fine either way. He outlined options: delete discussion of old versions and rely on version-control history, keep only the previous major version's discussion, or add a final 'what happened in 3.0' section with an introduction explaining that the text is written in the future tense. The last would avoid editing the rest.
No decision has been made on the lifetime of the content.