[cvsnt] import statement just hangs
tony.hoyle at march-hare.com
Sat Jun 7 20:54:58 BST 2008
> Well shucks!
> How do make other machines' directory structure match the original machine?
> For example, in the beginning (when importing . used to work) I did this:
> cd \
> mkdir business
> cd business
> cvs import -Cdn business root
> vi stuff
> cvs add stuff
> Then on the original machine, the path was business/stuff but on the other
> machines, it was business/business/stuff. I did not like the extra layer of
There's no reason at all why the other machine would be
business/business/stuff. What are you using for your checkout? In fact
the module name doesn't need to have anything to do with where it's
checked out, although it normally does for simplicity.
I have to admit I've never seen anyone create an empty module in that
way - although there's no reason it wouldn't work - normally you'd have
existing sources to import (cvs really doesn't have a standard way to
create empty modules.. my normal way is to checkout the root node and do
a cvs add).
More information about the cvsnt