In the case where a svn operation is interrupted in the middle, its best to
attempt to do a svn cleanup first, as that might actually pick up where it
left off and finish the operation. Checking out a fresh working copy is
probably the best method as long as you didn't have a bunch of modified
files in those directories that you'd have to copy back over. Subversion
always marks files with modified time as whenever you checked them out or
updated them.
- Jody
On 2/3/06, Dave Merrill <dmerrill@usa.net> wrote:
>
> Hello,
>
> TortoiseSVN crashed while I was trying to move everything at the top level
> of a working copy into a new folder I'd created there. It left some files
> moved and some not; I didn't do an exact inventory.
>
> I thought the best thing to do from there would be to revert to the
> previous
> version, but when I did that, the result was that all files were deleted,
> at
> all levels, leaving only empty directories, several of which were flagged
> for deletion judging by their icons.
>
> For safety's sake, I did a checkout from that prior version into a new
> directory, and that worked, but all files appear modified at the time I
> checked them out.
>
> Is this likely to be the best I can do from here? Any other ideas?
>
> Have other people had trouble doing this kind of move?
>
> Thanks,
>
> Dave Merrill
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
Received on Sat Feb 4 05:29:54 2006