From: Tom Copeland <tom@...>
Date: 2003-08-10T21:48:45+09:00
Subject: Re: CVS add

> I thought of that, but a friend advised against it. Quoting him:
> 
> | Never use cvs import on existing files. you'll get lost in a maze
> | of vendor ids and repository ids all alike.

That's a new one on me.  I've done many, many cvs imports without
experiencing problems... although I would agree that the documentation
for the cvs import command can be a bit confusing.  The really odd thing
about "cvs import" is that you have to be in the directory that you're
importing.  So if you've got a project foo:

foo/
 src/
 lib/
 doc/
 tests/

and you want to import it, you have to cd to inside the foo directory
and then run a:

cvs import -m "Importing the code" foo tom start

It's pretty counter-intuitive... but once you memorize it it's OK :-)

Yours,

Tom