***glaring*** flaw in cvs import?

[Robert P. J. Day]

  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.

  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"?

  i've verified that the directory is there in the source before the 
import, but it's not there once the import is done at the destination.
is this for real?

rday