Re: [PATCH v4 0/4] docs: document upcoming breaking changes

From: Junio C Hamano <gitster@pobox.com>
Date: May 31, 2024, 08:43 UTC
Message-ID: <xmqqr0dijrrh.fsf@gitster.g>
In-Reply-To: <cover.1717141598.git.ps@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> You may have noticed that I dropped the "Upcoming" prefix from
> "UpcomingBreakingChanges.md". This is supposed to reflect the fact that
> we also have a section that point out features that we are _not_
> deprecating. Those aren't upcoming, so I thought a rename makes sense.

I do not mind missing upcoming, but why markdown? The mark-up we as the project chose is AsciiDoc and unless there is a compelling reason to use something else, we should stick to it.

Yes, README.md is not AsciiDoc but that is primarily because what GitHub does on the project page.

$ 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.