[Top][All Lists]

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

Re: about imports and cvs update

From: Michael Haggerty
Subject: Re: about imports and cvs update
Date: Sun, 14 Mar 2010 12:27:39 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20090817 Thunderbird/ Mnenhy/

Harry Putnam wrote:
> I don't do many imports... maybe 5-5 in the last 10 yrs..
> And never did one that was not the start of a new repository.
> Is it a misuse of import to use it to start a new directory hierarchy
> beneath some exiting hierarchy in CVSROOT?

IMHO "cvs import" should only be used to create a vendor branch, which
is a branch that is used to actively track sources from a third party.
There is no need to use "cvs import" to get your own source code into
CVS, as it does lots of extra stuff that is useless when not tracking
third-party sources.  There are also several aspects of vendor branches
that are not recorded carefully by CVS, so the (ab)use of vendor
branches can make it harder to migrate away from CVS when that
inevitable day comes.

To add a new directory hierarchy within a CVS repository, simply check
out a working copy, copy the new directories to the right place in the
directory hierarchy, then use "cvs add" and "cvs commit" to put them
under version control.


reply via email to

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