On Mon, 17 Mar 2008 11:05:23 +0100, J.B.C.Engelen@...1578... wrote:
I am very much against doing offline 'commits', just from what I see happening in practice. Although it is nice to be able to 'save' work when there is no internet connection available, it removes an *essential* part from the workflow: SVN Update and checking whether it still works, possibly checking source code changes. I'm not sure whether everybody does this: 0. svn update
- code stuff
- svn update (!!!)
- make
- does it work? did merging go well?
- svn commit
2-5 in rapid succession and needs internet. This at least ensures that we don't get ';' missing buildbreakage etc, but also removes more complex problems. I think any offline CVS method removes 2 to 5.
This isn't a real issue; with a distributed SCM you still have to merge your local commits with upstream before the system will let you push them upstream.
-mental