On 29.01.2014 23:10, Gavin Lambert wrote:
> I was using TSVN 1.8.1 when the following sequence of events happened
> (this might be related to the other recent thread about this feature,
> which reminded me of this):
>
> 1. In the commit dialog, I marked a file as "restore after commit" and
> then used TortoiseDiff to modify it afterwards to revert several minor
> changes that I did not want to commit at the time.
>
> 2. I then remembered that I wanted to commit something else, so I
> unticked that file and ticked some other files and committed them
> successfully.
>
> 3. I reopened the commit dialog, noticed that the file was still in the
> same state as before (ie. it had the changes I wanted to commit before
> and not the other modifications), so I ticked it and a few other files
> and Committed.
>
> 4. The commit failed due to out of date WC, and prompted me to update.
> I did.
>
> 5. I checked the file again -- still only the changes I wanted to
> commit, so I let it commit. This succeeded.
>
> 6. I checked the file again -- now no changes from repo. I was
> expecting it to perform the "restore after commit" at this point and
> recover the changes I had reverted.
>
> I ended up having to recreate the changes. (Fortunately there weren't
> many and I still remembered them, so this was not difficult, but
> obviously this is not desirable behaviour.)
http://code.google.com/p/tortoisesvn/issues/detail?id=546
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3072329
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-01-30 19:11:32 CET