Re: Reorganized repository, cannot update

John Szakmeister wrote:
> So, I guess there are a couple of answers here to prevent losing your local
> modifications. You can go ahead and try to commit your changes (if they're
> ready to be committed). As long as someone hasn't done anything to cause a
> conflict, this should work without a problem. Or, you can run 'svn diff > /

Some of the changed files have had new revisions committed, so
unfortunately these can't be committed.

> path/to/somewhere/safe/local-mods.patch' to save off your current changes,
> remove the working copy, checkout a new one, and apply the patch with the
> 'patch' tool. You working copy will now have your local mods inserted back
> in.

This is what I'm trying to avoid.

Isn't there some way to turn my working copy rooted at /trunk/qmaster/
into a working copy rooted at / (revision 2122, where /trunk/qmaster
still existed)? I would think that would solve the problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 15 11:01:48 2003