RE: Re: Undo adds behaviour changed? No longer leaves files as unversioned

> If the file was previously unversioned then Undo Add should indeed
> return it to the unversioned state, preserving the file. I observe
> that behaviour on 1.7.5.
>
> If the file was SVN copied then Undo Add will delete it (via the
> recycle bin) since it is already version controlled.

I got caught out by this. Here's what happened:

1. In filesystem, rename an SVN-controlled file *and edit it*
2. Open TortoiseSVN 'Commit' dialog
3. Do 'Repair move'
4. Do 'Undo Add'
5. -> Commit dialog shows the new file as unversioned)
6. Press <F5> to refresh Commit dialog, or check the filesystem
7. -> The renamed file has gone and the local edits are lost!

Clearly step 5. above is a TortoiseSVN bug. It shouldn't show the file as unversioned when it's really been deleted.

But the real issue is that user data is deleted, without warning. IMO this should behave as it (presumably) did under SVN 1.6 client, with the new file being retained as unversioned, and regardless of whether it has local edits.

Note that this only affects 'copy adds'; undoing a regular add leaves the file unversioned as expected.

Cheers,
Jon E

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3007474

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-09-21 10:03:08 CEST