>
> 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 think that I want an in-place checkout of only the working base (ie
the .svn dirs). After that svn would tell you which files have changed
and you could commit them as normal. In other words, get a fresh copy of
the .svn folders without deleting the working files.
This would be the same as moving every working copy to a temp directory,
deleting everything, checkout, and then move the originals back where
they were on top of the newly-checked out files. This may seem easy, but
it can be an intensive manual process if you have lots of folders. Its
also a useless answer to a 'non-technical' user who will see it as a
serious weakness in the system.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 7 17:29:51 2007