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

Re: [TSVN] Re: "Update to Revision" doesn't count as a modification

From: Simon Large <slarge_at_slarge.plus.com>
Date: 2005-03-14 18:10:54 CET

Douglas Stonham wrote:
> On Fri, March 11, 2005 8:36 pm, Eric Hanchrow said:
>> Douglas> I realise that this isn't how you are supposed to "back
>> Douglas> out" changes but it still looks like very bizarre
>> Douglas> behaviour to me.
>> I think it's for when you want to temporarily look at the Way Things
>> Were. There's certainly no reason for the files to appear as
>> "changed" in the working copy. If you actually want to undo a
>> change, see
>> http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-4-sect-4.2.
> Yes, I'm familiar with using merge over reversed revisions. I wasn't
> the first time I hit this problem and I assumed it was just me, but
> since I recently met this again I thought I should mention it.
> I still don't know why this shouldn't mark the file as changed
> however.

The file isn't changed. It is exactly the same as the file in the repo.
It just isn't the HEAD revision.

> Imagine if you had updated a file to a previous version and then gone
> home for the weekend. On Monday, you have a project that looks like
> it is a perfect replica of HEAD, according to the overlay icons and
> the commit messages. You think everything is working, but another
> programmer complains it is broken.

Wrong! The overlay icons only tell you about changes _you_ have made
compared with the revision you got from the repo. To find out if HEAD in
the repo is any different you have to update, or just check for
modifications (click the 'check repository' button).

> Eventually, despite knowing that you are up-to-date with the
> repository, you try running update. Suddenly, your copy is broken
> too, but the log files for the server say that nothing was changed
> since your last commit.

Well that is exactly the same situation you get without doing anything
funny with old revs. If someone else commits a broken change to the
repo, you will not see it until you update your working copy.

> OK, so I'm probably overdoing the dramatic descriptions, but I still
> can't see why this results in a file marked as unchanged. Is it
> useful this way in some way I don't understand? Is it mimicking some
> behavious of SVN I wasn't aware of?

This is exactly the bahaviour of SVN. If it were to look in the repo for
changes, how often should it look? What if you are on a dialup line?
Will it dial up to check every time you browse a different folder in
Explorer? The WC is a sandbox. It doesn't change until you ask it to. If
you want to see what has changed remotely you have to ask for that too.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Mar 14 18:11:53 2005

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

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