[Top][All Lists]

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

RE: URGENT: Initial revision number for CVS.

From: Thornley, David
Subject: RE: URGENT: Initial revision number for CVS.
Date: Mon, 28 Jan 2002 15:02:37 -0600

> -----Original Message-----
> From: address@hidden [mailto:address@hidden
> Sent: Monday, January 28, 2002 8:46 AM
> To: address@hidden
> Subject: Re: URGENT: Initial revision number for CVS.
> I have a similar problem. At our company we have Sources that we want
> to put under CVS control. Some of the sources are already RCS
> controlled, so copying the *,v file directly into the repository seems
> to be the right approach for us. The history is preserved and 
> we get the
> revision numbers that have been created by RCS (which all have the
> syntax x.y, let's call this depth 2).
OK, no problem with that.

> No, importing the other, non RCS-controlled sources has the same
> effect that you describe. All files get the revision number,
> so the depth here is 4.
OK, no problem with that.

> We really do not need the depth 4 revision numbers and want a default
> revision number depth of 2. I have searched all the CVS manuals,
> Google and other written resources, but found no answer to this
> question.
Correction:  if you're doing a "cvs import" you do need the depth 4
revision numbers, and that's not just because CVS does it that way.
In imports, CVS maintains its own import branch, and since it's a
branch it needs depth 4.  Depth 2 revision numbers are only on the
head branch, and in an import situation are for your own changes.

Let me be more specific.  It may happen that you import a codebase
and maintain local changes to it.  We do it with Gnats.  In that
case, CVS has to have a way of keeping track of the changes in the
imported source versus the local changes.  CVS keeps track of such
things with branches, and so you need branches, and so you need
the revision numbers you're complaining about.  If you aren't
importing somebody else's source, but you're bringing in source
that will be developed from the CVS system, then you can use "cvs add"
instead of "cvs import".

> Has anybody an answer that is other than "don't care about the CVS
> revision numbers, use your own scheme with the use of tags" ?
What other answer is needed or accurate?  

reply via email to

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