[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

revision numbering within branches

From: Gavin McLeod <gavin.macleod_at_gmail.com>
Date: 2007-07-18 14:05:05 CEST


I've tried searching the mailing list in case this has cropped up before,
but couldn't find anything
so hope I'm not re-asking the same thing again!

We have a fairly standard svn setup, trunk being main development stream,
and we have branches
taken at live releases. Occasionally we have to make a patch to a branch,
but I notice the branch
doesn't maintain its own revision numbering separate from the trunk - I
assume this is normal svn

e.g., We make a branch, called release-1.0, at say svnversion 1000. We then
continue developing in
the trunk to say svnversion 1200, then we need to make a patch to live. So
we check out the branch,
make the patch and commit. The svnversion of the whole project (branch and
trunk) now becomes 1201.

This confused me somewhat, as I was expecting the branch to maintain its own
revision, as technically
it is now a separate work stream - ie I would have expected the branch
revision to become 1001, and the
trunk to stay at 1200, as we have only committed an update to the branch.

Is this normal for svn to maintain a single revision number that applies
across the trunk and all branches?
Is it possible to get svn to maintain separate revision numbering in
branches? or do people regard this
as a bad idea?

many thanks
Received on Wed Jul 18 14:04:40 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.