Re: Update to Revision vs. Revert to this Revision

Michael Hardt wrote:
> If I want to undo a bad commit . . .
>
> 1. If I go into the TortoiseSVN log , right-click on the revision I
> want to roll back to, and choose "Revert to this Revision," Tortoise
> updates my workspace. Then I can commit, effectively rolling back the
> repository.
>
> 2. If I just go into the context menu for my working copy and choose
> Update to Revision, Tortoise updates my workspace. Committing, however,
> has no effect--the commit dialog tells me there have been no changes to
> my files.
>
> I'm sure this difference is fundamental to SVN, but I'm missing it, and
> perusing SVN documentation hasn't clarified it. Would anyone be willing
> to shed some light on this?

http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-update.html

You can only commit items which are up-to-date with respect to the
repository. If you 'update to revision' this switches your working copy
to an old revision state. It is not really very useful except as a
snapshot of what the working copy looked like in a previous life. As far
as SVN is concerned, the files are unmodified (assuming they were
unmodified before the update-to-rev), but out of date.

"Revert to this revision" does a reverse merge of all recent revisions
into your working copy. SVN considers this to be an up-to-date working
copy but with local changes which just happen to make it look the same
as an earlier revision. Because it is up-to-date you are allowed to commit.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org