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

RE: rcs2svn?

From: Mats Nilsson <mats.nilsson_at_xware.se>
Date: 2002-11-01 09:05:40 CET

Karl Fogel [mailto:kfogel@newton.ch.collab.net]:
> ? Are RCS branch labels different from CVS branch labels? I thought
> they were the same thing, and even implemented in exactly the same way
> in the repository.

Vanilla RCS doesn't have labels on branches, only labels on file revisions.
But, labels are represented the same way in the repository.

When you make a CVS branch, cvs assigns a meta label to a non-existing
revision. Its purpose is to identify the branch, and to identify the next to
last version component of file revisions on the branch.

foo.c
  |
 1.1
  |
 1.2 'cvs rtag -b BRANCHLABEL'
  | \ BRANCHLABEL -> 1.2.0.2, where the last version component
  | \ refers to the third component in the revision version numbers.
  | 1.2.2.1
 1.3 |
  |

Thus, you can have multiple branches off of the same point. Each gets a
branch label. For instance, BRANCH_2 -> 1.2.0.4, with actual revisions in
the 1.2.4.x series.

RCS on the other hand has no automatic way of keeping track of alternative
branches off the same branch point.
In this case, the first revision on any branch would be 1.2.1.1. If several
branches would start from 1.2, there would be no way of telling to which
branch the 1.2.1.1 revision belongs.

I realize sorting out the revisions will be difficult. Got to do more
thinking about this.

Mats

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 1 09:06:52 2002

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

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