[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Thu, 31 Jul 2003 23:48:39 -0400
When you use the checkout command you are requesting to check out a module
from the repository and create a working directory. Unless you actually
have a module called dummy.c, which would be a poor name for a directory,
then this command should have always failed.
If you are using update and status then you must already have a working
directory in which case you probably don't want to use checkout since it
might cause you to lose changes in your working directory.
If you want to use checkout you should be creating a new working directory.
In general, the module name for a project is the same as the top-level
directory for that project under the cvs repository root directory. If you
have access to the repository machine check to see what the top-level
directory is that contains dummy.c and use that with the checkout command.
----- Original Message -----
From: "Y Hu" <address@hidden>
Sent: Thursday, July 31, 2003 10:59 PM
Subject: Re: checkout
> I've been using GNU CVS for a while on and off. In my
> last project, I used the the cvs command such as "cvs
> co dummy.c" for editing the file.
> Now, in my new project, the "cvs co dummy.c" gave me
> an error "cvs server: cannot find module `dummy.c' -
> ignored, cvs [checkout aborted]: cannot expand
> modules" despite that "cvs update dummy.c", "cvs
> status dummy.c" all works. Can anyone help me what I
> am missing here for cvs co command and how can I fix
> Thank you.
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> Info-cvs mailing list