On Mon, Sep 09, 2002 at 11:17:12AM -0700, Schwenk, Jeanie wrote:
> After the original import, why do you have to give the full path in the
> repository to where the imported files are to do? Is it because an import
> assumes nothing even when there are CVS directories?
Correct. An import of a tree with CVS directories is just like
an import of one without. (The CVS stuff isn't even a special
enough case to get "forcibly" ignored; as you've noticed, it's
just on the default ignore list like "*.o" etc.)
This is reasonable, given the command's name. Even if there is
CVS metadata, a command for "importing" stuff ought not to assume
it relates to your repo. E.g. it could be that you checked out
an open-source project over the Net, and you're importing the
code into your own repo to track your local patches. Just
because cvshome.org calls a particular module "ccvs" doesn't mean
you want to use that name :-)
"import" could arguably pay attention to the modules file -- but
I'm not going to be the one to argue for it :-) since (a) I don't
know what "pay attention to" would mean in practice, and (b) I
rarely use the modules file anyway.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
[...] despite reports to the contrary, it is the rare programmer who
permanently loses his sanity while coding ("permanently" being the
operative word).
- Eric E. Allen
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
