Odhams, David wrote:
> This has probably been discussed before but a quick search raised
> nothing.
>
> In short, creating a tag or branch based on your working copy may have
> an unexpected effect depending on whether or not you update prior to
> tagging even though there are no modifications on the repository.
>
> This is the scenario:
> 1: Check out the current version (from the trunk). Let us say this is
> revision R50.
> 2: Modify it and commit it, twice over say. The repository version is
> now R52.
> 3: Check the repository for modifications.
> 4: If there have been no modifications then create a tagged copy from
> the working copy
> (without switching the working copy to the new tag). This is R53 for the
> sake of the example.
> 5: The log and the graph both show that the direct ancestor of R53 is
> R50
> (not R52 as some might have intended.)
> 6: Properties of the working copy show that the last commit revision is
> R50.
> 7: Update the working copy (even though there is nothing new on the
> repository).
> The last commit revision is now R52.
> 8: Tag the working copy again. This is R54 in the repository.
> 9: The log now shows R54s ancestor is R52 (correct), the graph however
> shows a duplicated node R53(on the trunk) as an ancestor to R54 (wrong).
>
Which version are you currently using?
Can you check out the new tag and compare it with your working copy
(e.g., using WinMerge or some other directory comparison tool) please?
If it's not identical, then that's a bug.
Stefan
--
___
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
Received on Mon Nov 12 18:47:55 2007