Re: [PATCH v4 0/4] docs: document upcoming breaking changes
- From
Patrick Steinhardt <ps@pks.im>
- Date
- May 31, 2024, 11:15 UTC
- Message-ID
- <ZlmxaNF94XbaTxxY@tanuki>
- In-Reply-To
- <xmqqr0dijrrh.fsf@gitster.g>
On Fri, May 31, 2024 at 01:43:30AM -0700, Junio C Hamano wrote:
Show 13 quoted lines
> 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.
Oh well, fair enough. I'll convert it to AsciiDoc in the next version, but will wait a bit longer for feedback.
Thanks!
Patrick