Hi there,
Currently, the vim commit messages on github look like: > patch 8.0.0142 > Problem: Normal colors are wrong with 'termguicolors'. > Solution: Initialize to INVALCOLOR instead of zero. (Ben Jackson, closes #1344) A title with the patch number, a line for the problem, and a line for the solution. This is nice because the patch number is easy to read, and the commit message is easy to parse. However, many git tools assume that there's a blank line between the so called 'title' and 'body' of the commit messages. So I suggest instead to negate the 'problem' part, keep the solution' part as a body, and add a blank line. Thus the commit message would look like: > patch 8.0.0142: Fix normal colors when used with 'termguicolors'. > > Initialize to INVALCOLOR instead of zero. (Ben Jackson, closes #1344) I'm aware this may break existing scripts relying on vim patches message format, but this convention is widely used (git itself, the kernel, and everything written by Tim Pope[1]...), so I believe it's worth it. Note that I'm _not_ suggesting any other changes in vim development process. I simply think that this would allow any fork of vim using a different process (based on pull requests, for instance) a little easier when trying to backport complex vim features, as seen for example here[2]. [1]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html [2]: https://github.com/neovim/neovim/pull/5771 Cheers, Dimitri Merejkowsky -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
