Re:Empirical Evidence for the Value of Version Control?
by maw on Monday December 17, 2012 @08:52AM
(#4932219)
when you're bug-hunting, smaller single-change commits make it far, far easier to track down and kill the bug.
This is true, but with the caveat that each of those commits needs to basically work. If you have untestable commits, things work less well, and maybe it's worth having slightly larger commits so that they will be testable.
Re:Empirical Evidence for the Value of Version Control?
by steeleduncan on Monday December 17, 2012 @09:45AM
(#4932417)
Thank you. This looks like it will work well. The only problem is remembering not to push.
It would be nice to be able to work with two repositories in parallel. One repository for my development and the other one the "official" repository with larger commits, better commit messages and the guarantee that all commits work.
Re:Empirical Evidence for the Value of Version Control?
by cheald on Monday December 17, 2012 @09:59AM
(#4932480)
You might be interested in git-flow[1] which is a formalization of this workflow.
[1] http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flo...
A better workflow is to use feature branches to work on a feature, when when you're done with it, rebase and merge it back to master and create a tag for the feature. This gives you an easy timeline of what features or fixes were introduced when, lets you commit often without breaking master, and doesn't destroy your valuable commit history.