Re: ***glaring*** flaw in cvs import?

[Robert P. J. Day]

On Fri, 23 Jul 2004, Pierre Asselin wrote:

> 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.

that's useful to know, but it's still appalling that the default 
ignore list contains "core", which causes cvs to gleefully toss even 
directories named "core".  do i understand it correctly that there is 
no way to configure cvs to ignore some *file* patterns but not the 
same *directory* patterns?  if that's true, that's definitely one of 
the worst examples of software design i've seen in lots of years.

lord, you could use that in a programming class as a golden example of 
things not to do.  i'm starting to understand why so many of my 
colleagues won't touch cvs with a barge pole.

rday