[Top][All Lists]

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

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

From: Todd Denniston
Subject: Re: Is there a way to handle long revision numbers in CVS?
Date: Fri, 02 Mar 2007 09:00:19 -0600
User-agent: Thunderbird (X11/20060909)

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:

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

reply via email to

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