[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: What SHOULD happen here?

From: B. Smith-Mannschott <benpsm_at_gmail.com>
Date: Tue, 8 Jan 2008 07:08:24 +0100

On Jan 8, 2008, at 05:58, Robert Roessler wrote:

> As sometimes happens, I changed my mind and decided that I did NOT
> want the last change to a file (I wanted to "undo" the previous
> commit).
> So I used the TSVN context menu entry "Update to revision..." and
> selected the previous rev and ONLY that file. The "rollback" or
> whatever it should be called in SVN-land happened, but the overlay
> stayed as "Normal" ("Unmodified")... refreshes did not change this.
> My question is: is this the most reasonable thing to have happen
> here? If there isn't a special overlay for "Reverted" or something,
> shouldn't it at least show "Modified" - it is no longer "current"
> WRT the WC or the repo, right?
> This is with the 11652 32-bit nightly on XP SP2.

This is expected behavior. You've just created a working copy with
mixed revisions. The files in your working copy are all still
unmodified relative to their base revisions. It's just that they
don't all have the same base revision anymore.

The correct command to accomplish what you are attempting to
accomplish is "Revert changes from this revision". (If you want to
revert the most recent N revisions you can also use "Revert to this
revisions"). These commands will make the changes necessary to revert
the given revisions on your local working copy (much like the merge
operation). Subsequently you can then check these local changes back
into the repository. You'll find these two commands in the context
menu (right mouse button) for log entries in the window opened by the
command "Show log".


To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org

Received on 2008-01-08 07:08:49 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.