On Thursday 12 April 2007 11:09, Armin Lütkenhaus wrote:
> Hi,
>
> I encountered a strange effect in TortoiseSVN which I believe is at least
> an unexpected behaviour. I am not sure if this is really a bug, but I
> would like to know your opinion.
>
> Here the scenario:
>
> - Create a fresh repository (using the latest version of TortoiseSVN) on
> a local file system.
>
> - Create some file (say "test.txt") and import it to the repository.
>
> - Check out a working copy (latest revision), which includes the file.
>
> - Edit the file and commit. This should result in repository version 2.
>
> - Delete the file from the directory (using subversion delete offered by
> Tortoise menu), the commit, resulting in repository version 3.
>
> - Creata a new file with the same name "test.txt", add it to the
> repository again and commit, resulting in repository version 4.
>
> - Edit the file again and commit, resulting in repository version 5.
>
> Now "update" (in the working directory) to repository version 2. You will
> see the "old" file "test.txt".
>
> But: When you view the revision graph, you will see the file mentioned
> for repository revisions 4 and 5, but *not* any hint that such a file
> already existed in versions 1 and 2, although you are looking at the file
> which was present in repository revision 2!
>
> As I said, this does not seem intuitive to me and I really would like to
> know what you think about it.
It's a bug. I've filled an issue:
http://issues.tortoisesvn.net/?do=details&task_id=360
Tobias
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Apr 22 19:54:57 2007