Sounds like a feature much like git's "git stash"
On 21 December 2011 20:10, Randon Spackman <randon.spack...@hotdocs.com> wrote: > One of my common use cases for subversion is to want to split my changes > into two separate commits. In the past, I would do the following: > > > > 1) Check out > > 2) Make changes > > 3) Realize that this should be more than one commit > > 4) Copy directory “MyCode” to “MyCode2” > > 5) Revert changes I don’t want to commit yet from “MyCode2” > > 6) Commit “MyCode2” > > 7) Delete “MyCode2” > > 8) Update “MyCode”; already committed changes are merged and no longer > appears as diffs. > > 9) Commit remaining changes in “MyCode” > > > > Unfortunately, this use case is defeated by the 1.7 changes to a single .svn > dir. My current workarounds are as follows: > > 1) Copy the entire working copy (multiple GBs, waste of time), or > > 2) Do an “svn info” to get repo and revision, then check this out > somewhere to obtain the necessary “.svn” folder which is then copied to > “MyCode”. > > > > Neither of these is very elegant. I’d like to see a new svn command such as > “svn localize” (don’t keep my terminology if it sucks) that would make the > directory you specify its own independent working copy that can be copied > and manipulated individually, and possibly a “svn delocalize” to reintegrate > it. (Although this can be accomplished less effectively by simply deleting > the “.svn” directory and doing an update.) > > > > Is there already a way to do this? Thoughts? > > > > Randon Spackman