[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ***glaring*** flaw in cvs import?
From: |
Pierre Asselin |
Subject: |
Re: ***glaring*** flaw in cvs import? |
Date: |
Fri, 23 Jul 2004 00:43:28 +0000 (UTC) |
User-agent: |
tin/1.6.1-20030810 ("Mingulay") (UNIX) (NetBSD/1.5.4_ALPHA (i386)) |
Robert P. J. Day <address@hidden> wrote:
> following the instructions in "tracking third-party sources", i
> downloaded a kernel source tree that i both want to update regularly
> from the source, and make local changes to.
> i pulled down the tree, cleared out all CVS directories to turn it
> into a regular directory tree, then used "cvs import" to check it into
> my local repo.
Ok, so you checked out a tree from a public CVS server and you want
to import that locally. You don't have to remove the CVS/
subdirectories. See below.
> in the process of doing that import, the "cvs" command apparently
> decided it didn't much care for the kernel source directory
> net/bridge/core, and threw it away! why? because it's called "core"?
Because 'core' is in the default ignore list. I usually reset the
ignore list to just 'CVS', like this,
cvs import -I! -ICVS <path> VENDOR <release-tag>
and then check out a fresh sandbox somewhere else.
You can keep the original external sandbox untouched; that way, you
can update it from the public CVS server and reimport any deltas to
your internal server.
--
pa at panix dot com