Consensus Protocols: Two-Phase Commit at Paper Trail
Nice article on 2pcWho-T: On commit messages
About composing commits and writing commit log messages.
An opinion piece on what comprises a good commit message.
Any software project is a collaborative project. It has at least two developers, the original developer and the original developer a few weeks or months later when the train of thought has long left the station. This later self needs to reestablish the context of a particular piece of code each time a new bug occurs or a new feature needs to be implemented.
"In the last few weeks, I've had a surprising number of discussions about commit messages. Many of them were with developers new to a project, trying to get them started. So here's a list of things you should do when committing, and why you should do it."
An excellent list of best-practices for commit messages when using your favourite version control system.
good reasoning on howto, and hwo not to write commit messages