[Top][All Lists]

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

RE: CVS Version CHange

From: Jim.Hyslop
Subject: RE: CVS Version CHange
Date: Mon, 1 Dec 2003 10:18:19 -0500

Mark D. Baushke [mailto:address@hidden wrote:
> S.Magesh <address@hidden> writes:
> > Is there any way to change version in existing repository 
> i.e i have a
> > repository name MAC , in this repository the version of the 
> files are
> > 1.3,1.4 etc ... , Now our project developers are asking to 
> change the
> > version number from 1.3 etc to 2.0.
> Resist them.
> They should not care what a file's revision number is. Tell them that
> cvs uses version numbers internally and you should let it do what it
> does best. They should just write code and tag the versions with
> meaningful symbolic names like V2_0 when they want to give a version
> name to a collection of cvs controlled files.
> > All the exsiting files should display 2.0 ????
> No, let them use symbolic tags, but version numbers are NOT directly
> related to the external world.
Well, that depends on what the developers really want.

If the developers want to control the individual version numbers, then I'd
agree with you.

On the other hand, the developers may want to take the current state of the
repository, and assign it a known starting point, such as 2.0. This is
entirely reasonable.

> > How do i do this ???? Pls help me in this issue
cvs co modulename
cd modulename
cvs commit -r2.1

I strongly recommend that this be used *only* for the scenario I outlined -
starting a new major revision number. I do *not* recommend using it to
modify the minor number. In general the CVS revision number is unrelated to
the outside world - the only exception I would make is the major number; it
might be used to signify something special. As you say, though, the tags
provide a much more flexible way to signify that information.

> Read and understand:
I second that motion.

Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (
Columnist, C/C++ Users Journal (

reply via email to

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