info-cvs
[Top][All Lists]
Advanced

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

Re: revision numbers of files in a branch


From: Mark D. Baushke
Subject: Re: revision numbers of files in a branch
Date: Wed, 02 Nov 2005 23:04:52 -0800

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

Vidya Chandrasekaran <address@hidden> writes:

>        I am currently working on a 'cvs push and pull tool', the gory 
> details of which i shall skip. I have to process files in the working 
> directory based on the branch that they belong to, if they do.
> 
>        Now, cederquivist states
>        >> $ cvs tag -b rel-1-0-patches
>        >> [snip]
>        >>Note that the numeric revision number that matches  rel-1-0  
> will probably be different from file to file.
> 
>     I understand this to mean two files at the head of a newly created 
> branch may have A.B.C.X and A.B.C.Y as their version numbers.
>     Can i expect the A.B.C part to be same for both files?

No. Each file has its own set of revision number that are totally
unrelated to other files in the tree.

For example, if fileA was revision 1.14 when branch rel-1 was
created and fileB was revision 1.8 when branch rel-1 was created, then
fileA may have 1.14.0.2 as the magic CVS branch and the first commit
to the rel-1 branch would bump it to revision 1.14.2.1 while the fileB
would have a first revision of 1.8.2.1. Of course, if a branch beta-1
was added to fileA revision 1.14 and fileB revision 1.7 before the rel-1
branch, then you might see a 1.14.4.1 as the first commit to rel-1 for 
fileA...

>     Or do you suggest that going by tags would be a better idea. Either 
> way, it doesn't hurt to know.

Never make any assumptions about the internal CVS revision numbering
scheme.

> Thanks
> Vidya
> 
> PS: I can't help the legal(?) disclaimer. This is the only email account 
> i have access to. Apologies.

You may wish to get a gmail.com account...

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDabaUCg7APGsDnFERAhzYAKDygeWme4eNNN9LUUFfJkZltdFzKgCfSNbJ
xmB88CDci31HsyoTAQI94zQ=
=HsA0
-----END PGP SIGNATURE-----




reply via email to

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