IMO, Git commit messages serve two purposes: - inform the reviewer why the commit was made: to guard against spurious commits, they should mention all changes made - make it easier to find the commit when scanning a file's history
Most messages should be a single line. Sometimes there is a need for a bit more context to explain why the commit is being made. Any longer, and the commit probably mixes too many changes, and should be split. Git commit messages should not include explanations of how the code works. Such comments belong in the code source. It should not be necessary to delve into Git logs to understand why the code is written as it is. Remember that the ASF releases code as source, so any information that is necessary for the understanding of the source must be recorded in that source. Sebb.
