| |||||||||||||
Lessons from PostgreSQL's Git transitionLessons from PostgreSQL's Git transitionPosted Oct 13, 2010 22:42 UTC (Wed) by marcH (subscriber, #57642)In reply to: Lessons from PostgreSQL's Git transition by petereisentraut Parent article: Lessons from PostgreSQL's Git transition
> ... instead of a dozen crappy commits mixed with another dozen small cleanups "to serve the pure git workflow".
Abilities to rewrite and clean up history is where git shines more than any other similar tool. Developers with some basic git experience never let crappy commits survive long enough to escape their local hard drives.
(Log in to post comments)
Lessons from PostgreSQL's Git transition Posted Oct 14, 2010 1:15 UTC (Thu) by dmarti (subscriber, #11625) [Link] ...and some of the "crappy" stuff committed locally turns out to have actually worked, so you're more likely to get in the habit of committing small changes. (I don't like the Subversion model where "commit it to revision control" and "everyone else on the project can point at your code and laugh" are the same.)
|
|||||||||||||