Re:Our Git Workflow: Private Development, Public Releases
by loewenskind on Wednesday August 18, 2010 @04:52AM
(#1613600)
This is what I always liked about darcs (it's still the DVCS I use at home): separating checkins into logical change sets.
Good, logically separate changesets make merging, backporting (cherry-picking), bisecting and reverting much easier. It is worth the trouble.
The version history of the git project itself serves as a magnificent example of what a commit history should look like. It's actually possible to read the logs and understand each committed change. (Most of the time)