(no subject)

[Mark D. Baushke]

: "Aggarwal, Vineet" <address@hidden>
cc: address@hidden
Subject: Re: best way to create new project 
In-Reply-To: <address@hidden> 
References: <address@hidden>
Comments: In-reply-to: "Aggarwal, Vineet" <address@hidden>
   message dated "Tue, 03 Oct 2006 12:41:37 -0400."
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
X-Face: #8D_6URD2G%vC.hzU<dI&#Y9szHj$'mGtUq&d=rXy^L$-=G_-LmZ^5!Fszk:yXZp$k\nTF?
 8Up0!v/%1Q[(d?ES0mQW8dRCXi18gK)luJu)loHk,}4{Vi`yX?p?crF5o:LL{6#eiO:(E:YMxLXULB
 k|'a*EjN.B&L+[J!PhJ*aX0n:5/
Mail-Followup-To: info-cvs <address@hidden>,
 address@hidden
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 03 Oct 2006 16:55:09 -0700
Message-ID: <address@hidden>
Sender: address@hidden

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aggarwal, Vineet <address@hidden> writes:

> To create new project in a repository we first checkout the root of the
> repository (cvs co -l . ) then create a subdirectory for the new
> project, add files to it and commit. We don't use cvs import worrying
> that the vendor branch functionality will create branches and do
> undesired things. Is there a way to exclude vendor branch creation when
> using cvs import. Or is there some other better, more cleaner way to
> create new projects.

Your method is reasonable and is what I often do to create a new top
level module.

   cvs checkout -d top -l .
   cd top
   mkdir new-module
   cvs add new-module

You may now copy files and directories into the new module and=20
'cvs add' them as you wish.

While it is also possible to use 'cvs import' for this, it is just as
good and maybe even better to avoid the extra confusing tags that will
be created as a part of the cvs import process.

        Enjoy!
        -- Mark

=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFFIvhdCg7APGsDnFERAqN/AJ0eJ9THYZ0vZQlc60HT6vG3nfAs0wCfSH0I
wS2lLnGhqcDq0OjbWLaEUAM=3D
=3D7hIv
=2D----END PGP SIGNATURE-----