[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Moving RCS files to CVS - bad rev information

From: Kaz Kylheku
Subject: Re: Moving RCS files to CVS - bad rev information
Date: 17 Oct 2002 08:52:41 -0700

address@hidden (Dean) wrote in message news:<address@hidden>...
> Hi,
> I moved a large amount of RCS files into CVS and noticed that 
> all the symbolic revision tags now appear as branches.  When
> I do a 'cvs status' on a file there are no revision tags, just 10s and 10s
> of branch tags.

You must mean 'cvs status -v' which shows tag information.

> What did I do wrong?  Is it something in the setup of my RCS files?

You are assuming that CVS ,v files have exactly the same semantics as
RCS ,v files due to sharing a common syntax. However, CVS branching is
somewhat different from RCS branching. Branch revisions are
represented using special numbers that have a .0. component, e.g. if
you have and, it indicates that two branches are
sprouting from version 1.4, branch 1.4.2 and 1.4.4.

It looks suspiciously like someone played silly games with RCS
revision numbers; I don't think RCS ever generates version numbers
containing zeros unless it is told to.

> I just copied the ,v files directly to the repository.
> Is there a method to turn a branch tag into a revision tag?

You must edit the revision number, since that property is encoded in
its structure, as you can see.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]