[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why is revision on 1st import 1.1.1.1 instead of 1.1?
From: |
Greg A. Woods |
Subject: |
Re: Why is revision on 1st import 1.1.1.1 instead of 1.1? |
Date: |
Sun, 24 Jun 2001 14:01:07 -0400 (EDT) |
[ On Sunday, June 24, 2001 at 13:40:56 (+0200), Felix von Delius wrote: ]
> Subject: Why is revision on 1st import 1.1.1.1 instead of 1.1?
>
> 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!
RTFM! ;-) It's all in the manual.
(your quick, serious, hint is because the "cvs import" command is
designed to create a vendor-branched module -- 1.1.1 is the vendor
branch on which you commit, er, import, third party code to)
--
Greg A. Woods
+1 416 218-0098 VE3TCP <address@hidden> <address@hidden>
Planix, Inc. <address@hidden>; Secrets of the Weird <address@hidden>