> Perhaps this can be considered stupidity, but windows nor SVN deny
> this possibility, so i'll consider it a dangerous bug.
> Imagine this folder structure, containing svn repositories as
> |- Repo1/ -> (http://www.repository-1.com/sub-repo-1/)
> |- Repo2/ -> (http://www.repository-1.com/sub-repo-2/)
> |- Repo3/ -> (http://www.repository-2.com/sub-repo-1/)
> |- Repo4/ -> (http://www.repository-2.com/sub-repo-2/)
> Notice that Repo1-2 refer to http://www.repository-1.com, and Repo3-4
> refer to http://www.repository-2.com.
> Repo1-2 obviously share HEAD revision number, as do Repo3-4.
> I want to update my code, so I select all 4 folders, right click ->
> SVN Update.
> What happens is, SVN Update is performed on all four folders using the
> HEAD revision number from the *first folder only*.
TortoiseSVN updates all selected items to the same revision, but ONLY if
all repository uuids are the same.
TSVN does this to avoid a race condition: if it would update all to HEAD
and they're all from the same repository, they could end up with
different revisions if someone else does a commit between updating e.g.,
* update folder1 to HEAD (100)
* user2 commits to repository
* update folder2 to HEAD (101)
If TortoiseSVN updates all your selected items to the HEAD revision of
the first selected item but those items are not from the same
repository, then your repositories are set up wrong: they all have the
same uuid which is NOT what they should have!
(it's called an uuid for a reason).
Please fix your repositories so that all have a real uuid (a UNIQUE id).
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-01-01 09:14:50 CET