RE: Darcs-style interactive commits,

From: Steve Strobel <steve.strobel@link-comm.com> [mailto:Steve Strobel
<steve.strobel@link-comm.com>]

 [snip]

>If I have a lot of files with overlapping changes, I copy the entire

>working copy (or at least the sub-tree that contains all of the

>changed files) using the file system, not SVN's copy. I then start a

>commit in each and revert all but the logically-related changes in

>each. Finally, I delete one working copy and do an SVN update on the

>other, which pulls in the other set of changes. The drawback to this

>method is that if you revert a change in both working copies, you

>loose it forever. One way to avoid that is to make a third

>copy. Don't revert anything in it; just update it after committing

>from each of the other copies. Anything you haven't checked in yet

>should show up as a modification.

In my travels, I have found that robocopy (on Win32) can be extremely
helpful when making copies and moving things around, whether on the client
or server.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 6 15:31:56 2006