On Mon, May 01, 2006 at 10:13:22PM -0500, Ross Day wrote: > Maybe I'm misunderstanding...but since when do you need a network > connection to use SVN...if you really want, keep your repository on your > laptop and work on a working copy checked out from it. > > For that matter, ANY source control requires networking...because the > whole point is sending it some central repository.
You are misunderstanding. The point really isn't just maintaining my own files. Consider working on a project. For example, I contributed to the seppl kernel module for a while. Now he had CVS, which is neither here nor there since that one doesn't seem to be on anyone's list as "modern". But what would have been very helpful to me would have been this workflow: 1) connect to internet and check out current seppl work 2) while offline, work on my changes and make local commits 3) from time to time, sync up to follow unrelated changes that the main author is making 4) more work offline (resolve conflicts, etc.) with local commits 5) Ultimately, I'd like to be able to present the author with a diff against his cutting edge working tree so he can merge in my changes with minimum trouble. I was able to do this by hand in very clumsy ways at the time, keeping my own changes in a local revision control. Whenever I wanted to merge in his latest changes, I basically had to check out his latest branch, compute the diff within my own work on my local RCS, and apply it by hand to his files (then clean up the bad spots). Contrast with Darcs or Git, where I could basically work offline, but connect periodically and let the SCM merge in the orignal author's continuing changes. Don -- Don Bindner <[EMAIL PROTECTED]> ----------------------------------------------------------------- To get off this list, send email to [EMAIL PROTECTED] with Subject: unsubscribe -----------------------------------------------------------------
