For example:
----------------
improve Buffer Cache Management & logging
- change 'tryDrop()' to skip immediately, if lock unavailable
- move BufferCache logging to a separate logger
- attach BufferTrim.Unsuccessful -> Preemptive Flush of oldest buffers
--------------------------------
Having worked in many codebases & internal docs, I've found narrative significantly less efficient to read & write.
In commit messages, far too many developers skip almost any detail as to what they're changing & why -- the slowness of narrative formats may substantially contribute to this. In docs (Wiki etc), narrative encourages developers to ramble about minor technical details while omitting all high-level context.
Headline + bullet-points bypass a lot of struggles with narrative by allowing a simple headline and then, well, cutting to the point.
This also illustrates a informed personal preference -- studies find lowercase English words faster to scan/ comprehend.
See: http://literatejava.com/git/how-to-write-a-good-git-commit-m...