[vim/vim] Deterioration of commit message formatting (Issue #21330)

12 views
Skip to first unread message

dkearns

unread,
Sep 17, 2026, 3:19:44 AM (yesterday) Sep 17
to vim/vim, Subscribed
dkearns created an issue (vim/vim#21330)

Over the last few months it appears that the formatting of commit messages has deteriorated significantly.

Traditionally, Vim has formatted messages as short, single-sentence, "Problem:" and "Solution:" statements, with further elaboration in the body of the message if required. See :help patches-9.1 for examples. Problem and solution statements are now frequently formatted as multiple long sentences well over 500 characters.

The traditional format is a real feature, enabling rapid visual scanning of the patch history. If the current worsening trend continues and the help format is still considered valuable, some poor sod is going to have to reformat the rambling messages before release.

Beyond consistency of length and tone some problem statements make little to no sense without the context of the commit header line, which has traditionally just been a clone of the problem statement and is disregarded in other contexts like the help patch list.

I'm unaware of any change in policy, so I assume this is the result of LLM-generated commit messages. I don't think these have any place in a project like this and they should be disallowed. This is the thin end of the wedge.


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/21330@github.com>

h_east

unread,
Sep 17, 2026, 8:26:03 AM (20 hours ago) Sep 17
to vim/vim, Subscribed
h-east left a comment (vim/vim#21330)

I've updated the commit messages and PR descriptions for a few of my PRs that came to mind.
If there are any others remaining, please tag me directly with my ID.


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/21330/5714312874@github.com>

Christian Brabandt

unread,
Sep 17, 2026, 3:03:09 PM (14 hours ago) Sep 17
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#21330)

Yes, I have also noticed this, but it did not care too much about this. In fact I actually liked that the Problem/Solution line were a bit more detailed, as I thought this describes the changes more accurately. But I can definitely work on shortening the commit messages more into the former brief Bram format.


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/21330/5719713907@github.com>

Reply all
Reply to author
Forward
0 new messages