Wolfgang Kastaun wrote:
> Hi !
> I recently did the following:
>
> cp -R grh grh_try (grh was a svn working copy of a directory)
>
> This was meant to be a throw away test not to be versioned. But the test
> worked very well and I continued working on it. Then came the MISTAKE: I
> forgot that I used cp instead of svn copy to create grh_try and did:
>
> svn add grh/dm50 (a subdirectory)
> svn delete grh
> svn move grh_try grh
>
> This gave some errors wich I did neither understood nor remember. Did:
>
> svn --force move grh_try grh
>
> This seemed to work first. But later I discovered that the dm50
> subdirectory in grh was not in the repository, and a "svn st" said
> it was not under version control. On the other hand "svn add dm50" said
> it was already under version control, and did nothing.
>
> I now fear that my repository could have become somehow corrupted by
> that mistake. So my question:
>
> When I check out a new working copy and add this dm50 directory again,
> is everything in a consistent state afterwards or do I have to expect
> more trouble with this repository ?
No, you shouldn't have any problems with the repository.
I would check out fresh working copies, copy any modified files from the
older working copies to the new one, commit them and delete the older
working copies that had these changes made to it.
BTW, when I do make a copy of a working copy to try something in, I
always copy the entire working copy, not a subdirectory of the working
copy, which is asking for trouble like the one you ran into.
Regards,
Blair
--
Blair Zajac, Ph.D.
<blair@orcaware.com>
Subversion and Orca training and consulting
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 20 19:06:57 2005