> It appears that a copy created by ctrl-left-drag in TortoiseSVN repo browser behaves differently to a copy created by branch/tag from working copy.
> The revision number reported by repo-browser for a copied item increases when you do a repo browser copy (i.e. the copy target displays a higher revision number than the copy source), but does not increase for the copied items after a branch/tag (i.e. the items within the result of the branch/tag display the same revision numbers as the original source items).
> This is a bit surprising and a bit annoying especially when you want to use the $Rev$ property. We would like the $Rev$ number to remain the same when we extract each of those items, but the item created by repo-browser copy gets a higher $Rev$.
> You might wonder why it matters, and usually it does not, but we have one unusual circumstance in which it would be much more convenient if the revision numbers matched.
> Is there a way to make copies in repo-browser without increasing the $Rev$?
> Or is working copy tag/branch the only way?
Please read the first chapter of the subversion book to understand the
basics of repository revisions and mixed revisions within working
Any copy, however made, will create a new repository revision. If you
create a branch/tag from your working copy but do not check the
"Switch to new branch" box, you will create a copy, but your working
copy will still be on the original source, with the original mixed
revisions. If you update the working copy you will get consistent
revision numbers, but still on the original source. If you switch you
will get the new branch and consistent revision numbers.
: 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-02-13 12:58:17 CET