Bolstridge, Andrew wrote:
>
>
> It has nothing to do whether it was my fault, or subversion's fault. I
> only care about being able to fix it easily and without fuss. As other
> people have pointed out, the WC is pretty fragile, so this cannot be an
> issue for a few people. Making it more robust isn't practical (or even
> possible?) so the next best thing is to provide tools to make repairs.
I'm not opposed to such a fix but I don't see how it is practical. The
system already knows how to construct a new, complete checkout of
anything you have committed. As long as your .svn directories are
intact it can tell what else you have changed. However, there is no
limit to what you can do to the .svn contents and no way for the system
to tell or fix that short of comparing to what a fresh copy would
contain, which would end up being more work than just making that fresh
copy in the first place. Can you suggest a practical mechanism that
would help? I suppose if you are on a low-bandwidth connection, some
rsync-like transfer might be able to take advantage of what you still
have, but it still isn't going to be able to tell changes you might want
to keep from ones that are accidental.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 7 15:05:59 2007