Hi One of our users asked me a question this morning that revealed that I don't fully understand revision numbering in svn. So I would like to ask for explanation please.
With the trunk at revision n, he created a tag using svn copy -r HEAD. So I guess the tag was at then at revision n+1. He then committed some changes to the trunk and realised that he wanted those changes to be reflected in the tag also. The trunk was then at, say revision n+2. He did the following in his tag folder in the working directory: svn up -r n+2 --force It seems that the tag was then at revision n+2, but the tag did not contain the files committed at n+2. I realise this reflects some muddled thinking about how svn works. Please can someone explain why the tag did not inherit the latest changes? (I guess a merge would be appropriate, but why exactly did the update not have the intended effect). Best regards David
