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 ->
What happens is, SVN Update is performed on all four folders using the
HEAD revision number from the *first folder only*.
Imagine repository-1.com is at revision revision 50, and
repository-2.com is at revision 1000;
* The 2 folders referencing repository-1.com are updated to revision
* The 2 folders referencing repository-2.com are reverted back to
revision 50 (deleting practically everything in my case) and making a
terrible mess where i have made changes.
I made a mess, lost some code, and had to re-do some work.
Obviously i know now that it's dangerous to multi-select and Update,
but that's certainly not intuitive.
Windows and TortoiseSVN allow multi-select, so i expect that it should
be safe to do, i imagine i'm not the only one who's made this mistake.
Also, it's a little tedious to have to right click->Update each folder
separately wherever i can't be certain that every folder references
the same repository.
Could TortoiseSVN please be made to consider each folders head
revision separately, not apply the first head revision number to all
(This also applies to some other SVN operations too it seems)
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-01-01 08:41:49 CET