[vim/vim] doc: Per-patch documentation absent since 9.1.2148 (Issue #19566)

hseg

unread,

9:35 AM (10 hours ago) 9:35 AM

to vim/vim, Subscribed

hseg created an issue (vim/vim#19566)

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
Since version 9.0.2190, version9.txt hasn't been updated with the per-patch Problem/Solution descriptions. This makes it harder to follow along with changes in vim's development.

Describe the solution you'd like
A return to the prior policy of documenting the patch history.

Describe alternatives you've considered
One could keep a copy of the vim Git repo and use its history-browsing features. However, this is a channel in parallel to the Vim releases -- another source to check and keep up to date, when the distribution work has already been done by packaging up a patch release.

Additional context
It may be I just couldn't find the ticket where it was decided to only provide the headline changes for 9.2 and above, but the presence of patches-after-9.2 suggests that that wasn't a policy change?

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

10:42 AM (9 hours ago) 10:42 AM

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19566)

Those patch descriptions typically only happen shortly before a release, e.g. commit 1ff963e for 9.2 release and commit 5872bcb for 9.1

You can always check latest version in this repo here: https://github.com/vim/vim/blob/master/runtime/doc/version9.txt

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

10:44 AM (9 hours ago) 10:44 AM

to vim/vim, Subscribed

Closed #19566 as not planned.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

hseg

unread,

11:02 AM (8 hours ago) 11:02 AM

to vim/vim, Subscribed

hseg left a comment (vim/vim#19566)

OK, then I misunderstood. At what cadence are these kinds of updates usually made? Is there some tooling that generates these, that could be used when packaging patch releases?
The link to the up-to-date version9.txt doesn't help, since as you say, it seems to only be touched in big history dumps and changelog edits, not synchronously with the merging of patches.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

11:37 AM (8 hours ago) 11:37 AM

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19566)

New features are always updated directly to version9.txt. Each and every numbered patch is not. This is only updated before a release.