Re: Is there a way to handle long revision numbers in CVS?

[Todd Denniston]

Jijo Thomas wrote:
> Hi All,
>
> I've been working on building a wrapper over CVS to create a Source Control
> tool that will be used by my oraganisation. One among the requirements is
> the ability to branch too often. i.e, Every time a developer works on a
> problem, she'll be doing to in her own private branch. Once she is pretty
> sure that her code works, she'll merge it to the parent branch. This would
> create a huge number of branches off branches. This means that the revision
> numbers for such files can get long. And cvs log could show some cluttered
> revision numbers.
>
> I have 2 questions,
>
> 1. Can we hide such a long revision numbers to something short?
> 2. One of other requirement of our tool is the ability for an automatic
> patch building system to pull out any revision of a file. With such
> arbitrary branches created it would be difficult to select one particulaer
> revision. Is there any way with which we can specify say, i need 3rd
> revision from the branch 'ui_change' when the file has 10 revisions on the
> branch 'ui_change'.
>
> Please help.

both questions have the same answer:
Use tags and ignore the revision numbers CVS uses internally. (ignore the man 
behind the curtain.)

specifically for number 2 you can have the people (or a script) apply tags of 
the order ui_change_1, ui_change_2, ui_change_3 ... ui_change_10, at 
appropriate times after appropriate commits/merges.


some relevant URLs:
http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_4.html#SEC44
http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_4.html#SEC48
http://ximbiot.com/cvs/wiki/index.php?title=CVS_FAQ#What_is_the_best_branching_practice_to_use_with_CVS.3F

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter