I imagine a diff against the last CVS before the change should apply cleanly to the new SVN immediately after, shouldn't it? As far as I'm aware, it's not a rearrangement of the tree, just a change in the tool we're using to store it, right?
On 12/23/06, Michael Sevakis <[EMAIL PROTECTED]> wrote:
How will the movement of any changes in the local cvs tree not yet committed to svn work? What about patches? I suppose I can do a new checkout and apply my changes as a patch to the svn checkout? I'm asking for myself and on behalf of anyone else with a significant investment in new code. Michael
