Re: Why is revision on 1st import 1.1.1.1 instead of 1.1?

[Charles Sutton]

On Sun, 24 Jun 2001 address@hidden wrote:

>
> I have a question about a CVS behaviour that makes me wonder for a
> long time. When I import some files with the following command:
>
>   $ cvs import -m "1st import" some/path/in/repository mygroup start
>
> their revision numbers are all 1.1.1.1 - after a change+commit they
> become 1.2, but why aren't they they 1.1 before? Is there a way to
> make them 1.1 immediately on import?
>
> Any hints appreciated!
>

Hi,

Really short answer: This is normal behavior.

Short answer: In general, revision numbers are internally used by
cvs.  Don't stress about them.  In particular, revision 1.1.1.1
(and everything on the 1.1.1 branch) has a special meaning
to cvs.  A revision 1.1 does exist in your files, and
it's the same as 1.1.1.1.  You do not want to try
to change this.

Long answer: The 1.1.1 branch is used for the vendor branch
feature of cvs.  (Ever wondered why you need the mygroup and
start args to import?)  Please see the documentation on
vendor branches for more information.

(Hmmm... why is the short answer longer? :-)

HTH,

Charles