info-cvs
[Top][All Lists]
Advanced

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

Re: Revision Problem


From: Karl E. Jorgensen
Subject: Re: Revision Problem
Date: Fri, 25 Jan 2002 11:49:05 +0000
User-agent: Mutt/1.3.25i

On Thu, Jan 24, 2002 at 11:43:21PM -0800, seyethu Abthagir wrote:
> Hi All,
> 
> I have created new directory structure for my project
> and imported it into the CVS repository using "import"
> command on Linux.
> 
> I can see the Revision number as 1.1.1.1, when I
> checking out the imported .cpp files. But, I don't
> want the Revision number to be as 1.1.1.1 and I want
> the Revision number to be start with 1.1 as such.

This is standard behaviour for CVS. It actually creates both version 1.1
and 1.1.1.1 of the files (which happen to be identical). The 1.1.1.1
version is on the "vendor branch".

The revision numbers should not really be taken as having much of a
"meaning". I find that just letting CVS do it's own thing with the
version numbers works. If you want to assign any meaningful labels to
the version numbers, tags are the way to go.

If you reall, reall, really want the version numbers to start with 1.1
and never want to see an 1.1.1.1 version, they you may be better off
performing an *empty* import: 
  - Create a new directory 
  - import the newly created (and still empty) directory.
  - check out the newly created project somewhere
  - copy your existing files into the new sandbox
  - add all your new directories and files
  - cvs commit.

This should give you version 1.1 of everything.

> It would be appriciated, Could any one of u give me
> solution to erodicate this problem as soon as
> possible?
> 
> Thanks in adv,
> abu.

-- 
Karl E. Jørgensen
address@hidden
www.karl.jorgensen.com
==== Today's fortune:
BTW: I have a better name for the software .... Microsoft Internet
Exploder.
        -- George Bonser <address@hidden>

Attachment: pgpUs_FULpgcu.pgp
Description: PGP signature


reply via email to

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