[Top][All Lists]

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

Re: obtain revision information

From: Olav Lindkjølen
Subject: Re: obtain revision information
Date: Tue, 29 Jan 2002 14:09:05 +0100
User-agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1

The revision numbers are internal to cvs. Thats cvs's responsibility and nobody should pay any attension to them as anything other than a view into cvs's internal bookkeeping. If you look at the existing tags, o0-02, o0-03, v5-8-6, v5-8-7, and so on are Tags created at some point in the development process, when the developers felt the code in the repository needs some mark to go back to, or retreive later. Like a version release, or a bugfix release of the code. These tags are what's realy important to you. That allows you to retreive some earlier state of the source code based on a name (the tag name), which is entirely up to you to define the meaning of.

I dont know if this made things any clearer, but please forget about revision numbers. Trying to change them or understand them is like trying to change your social security number because you want it to match your phone number or Name and address. Leave them alone. They are cvs's territory. Instead you should set up a meaningfull tag naming scheme that makes sence to you.

Regards from Olav!

Harry Putnam wrote:

address@hidden (Larry Jones) writes:

Harry Putnam writes:

How can I get the current revision number of a package (module)?

CVS is a *file* versioning system, it does not have any concept of a
revision number for any larger package.  Most people use tags to
identify higher-level version information, so perhaps doing a status -v
on a file to list those tags will provide some information.  If you did
that on the CVS source repository, for example, you'd see tags like
cvs1-10-7, cvs1-10-8, and cvs1-11, which correspond to the 1.10.7,
1.10.8, and 1.11 releases of CVS.

Thanks Larry, that makes it quite a lot easier to find out version
stuff.  Still a little confused about what some of the output means

Following your suggestion, I thought to run `cvs status -v' on the
ChangeLog of the busiest directory in the package, might be a way to
get the needed info most efficiently.  And it does give some info,
but this output puzzles me a bit:

File: ChangeLog         Status: Needs Patch

   Working revision:    6.1143
   Repository revision: 6.1152  /usr/local/cvsroot/gnus/lisp/ChangeLog,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

   Existing Tags:
        o0-05                           (revision: 6.1104)
        o0-04                           (revision: 6.969)
        o0-03                           (revision: 6.421)
        o0-02                           (revision: 6.410)
        v                               (revision: 6.408)
        o0-01                           (revision: 6.406)
        v5-8-8                          (revision: 5.742.2.2)
        v5-8-7                          (revision: 5.522)
        v5-8-6                          (revision: 5.427)

Should there be a 5 digit gap between Working and Repository?
Then where existing tags are displayed, the most recent revision is some 40 less than Reporsitory revision.

A couple of other things I notice:
1) It seems the difference between Working and Repository should be 1.
   Not really sure what those terms means either.. both are committed

2) There seem to be somewhat random jumps between versions where tags
   were done.  I guess that doesn't follow any particular sequence.
   Maybe just whenever the committers or maintainers feel it will be

Info-cvs mailing list

reply via email to

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