4 ms·
Auto-commit after every save would likely break the build for other developers on the team.
by dennisgorelik 14y ago
Auto-commit after every save would likely break the build for other developers on the team.
- dalke 14y agoUnder some version control systems, you can commit to your own local repository, which no one else uses. When you're ready, you can push your repository out to others. With Mercurial, git, and other such system, you can auto-save without affecting others. Only when you push to trunk (if that's your development model) could you break the build.
- dennisgorelik 14y agoSorry, I forgot about distributed source control systems... Yes, such system (keep EVERY version in source control) might be convenient to work with: no need to think about when you need to commit your code changes. The code history switches from being "set of isolated snapshots" into kind of movie.