RE: Bug with 1.4.7, Build 11792

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Alborz Geramifard,

You wrote:

> Hi folks
> Here is how I could generate a bug on svn 1.4.7, Build 11792:
> -> Make sure the repository contains more than 3-4 revisions.
> -> Update to the latest revision.
> -> Revert back to 2-3 previous version.

whatever you call "revert"... :)

In Subversion terms "revert" means reverting (undoing) uncommitted changes in you working copy. I guess "revert" in your case means "update to revision x" where x < HEAD revision. Did you choose "update to revision" from the context menu?

> -> Update to the latest revision again.

> Result:
> You will be on the final revision number, while your
> files will remain
> on the version that you reverted back to!

No bug, normal behaviour.

If you turn on the "SVN revision" explorer column, you will notice that files have different revisions all the time. This number references the revision in which the last change was made to the file. Even though your entire working copy is updated to revision x, all files inside can have revision numbers from 1..x.

Cheers
- - Lübbe

- --
       ___
  oo // \\ "De Chelonian Mobile"
 (_,\/ \_/ \ TortoiseSVN
   \ \_/_\_/> The coolest Interface to (Sub)Version Control
   /_/ \_\ http://tortoisesvn.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFHsBYPm8gezyP1EasRAiuOAJ0TUnThvkMtRP02Rrx3nXA3OhYqmwCfY7TX
I7HMA6lkxe3BmIJmB2klgxA=
=Rrh0
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-11 10:32:21 CET