Re: An RCS files viewer?

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Spiro Trikaliotis <address@hidden> writes:

> * On Tue, Feb 21, 2006 at 01:44:06PM -0500 Jim Hyslop wrote:
>  
> > Spiro Trikaliotis wrote:
> > > am not sure if it will work if you have used RCS branches, as CVS
> > > branches are different.
> > 
> > How are they different?
> 
> Whenever I branch in RCS, the branch is done immediately (for example,
> branching on 1.7 will yield in the branch 1.7.1, and the first check-in
> on that branch will be 1.7.1.1).
> 
> Whenever I branch in CVS, only a tag will be generated (1.7.0.1). Only
> when I check in something, the RCS branch (1.7.1) will be generated and
> the checked-in version will be 1.7.1.1. That tag with "1.7.0.1" revision
> is completely missing with "pure" RCS.

CVS will only use even numbers in the 'magic' branch tags (1.7.0.2). RCS
does not mind if there are tags that point to revisions that do not
exist. So, to RCS the 'magic' CVS tags are just ignored.
 
> I am not sure if ViewCVS (and other tools) depend upon a tag with a
> "zero" in its revision number to recognize a branch. If they depend on
> this, they might not show the RCS branch correctly (or at all).

Nope. In fact, I believe that ViewCVS actually uses the RCS 'rlog'
command to obtain its information concerning the ,v file in the CVS
repository.

A normal RCS file may be used in a CVS repository with no ill effects.
It is even possible to use the 'cvs admin -b' command to change the
default branch to be an RCS branch like 1.7.1.14.1 if you needed to do
that kind of thing for some reason.

To the best of my understanding) CVS (as well as CVSNT) has taken pains
to not violate the RCS ,v format and only extended it using the existing
RCS extension semantics.

        Enjoy!
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFD/LDtCg7APGsDnFERAheJAJ9EUKWIiICviQ1UesqePzRpvZSNWgCgl1wx
7cwLlQHpgjdL7W0wudWmJIA=
=jceo
-----END PGP SIGNATURE-----