Roberto Nucera wrote:
>And this is true, I did an svn update, but what could have caused this
>branch to be at 44,
>since all it's local revisions are less than 44?
>
>For you information, this is a "branch" not the trunk. Could it be
>that the trunk is at 44? and so this branch also is at 44? Any other
>reason as to why this could happen?
>
>
Yes, that's exactly the case. There is only one current/most recent/HEAD
revision number for the *entire repository*. If the repository is at
revision n, and you commit changes to just one file, then *all files*
are now at revision n+1, whether they are in the trunk, a branch, a tag,
etc. Most of those files didn't change from revision n to n+1, but their
revision number increased nonetheless.
For what it's worth, Subversion places *no relevance whatsoever* on
trunk vs. branches vs. labels. They're all just directories in the
repository.. it's the people who use those different locations that
attach the meaning to them. Once you wrap your head around that concept
it's much easier to see how changes in the trunk can affect the revision
numbers of branches. (In fact, at my company, "trunk" and "branches"
don't really fit our model of workflow, so we don't even use them.)
As Sean suggested, you should read up on the relevant sections on "SVN
for CVS users" as well as the part explaining what revision numbers mean.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 30 06:12:25 2005