You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the simplest literal terms possible, a commit represents a change to lines of code in a revision control system, along with a description. The mechanics of most VCSes don't prescribe anything beyond that simple model. It's a concept that has been in use (and [misuse](http://www.nongnu.org/cvs/)) for a little over [40 years](http://en.wikipedia.org/wiki/Source_Code_Control_System), and a central concept in every major version control system ever released. Given that, and the fact that you're reading this document, and the fact that this document is *in* a revision control system, you're probably already familiar with this concept.
4
5
You are probably also familiar with people making "[bad commits](http://www.commitlogsfromlastnight.com/)", but what you might not be familiar with is a team that makes only "good commits", and more particularly the organizational implications of doing so. This document aims to explore those implications.