Re:Lessons from PostgreSQL's Git transition
by grammaton on Tuesday October 19, 2010 @09:28AM
(#1807022)
Sometimes it's absolutely critical for tracking down bugs - going back through the previous versions to locate which exact commit introduced an error can be a huge time saver, and sometimes the only way to track an issue down in a reasonable period of time. Even if that isn't something that happens for your project very often, I tend to think of commit history as being much like insurance - it's better to have it and not need it then need it and not have it.
[ Parent
| on HN ]
There are no comments on this comment yet.