Re: checkout

[Mark Priest]

Since the files you are checking out are read-only the cvs administrator has
probably turned on the watch/edit feature.  You should use the cvs edit
command on files that you want to edit (i.e. cvs edit dummy.c).  This will
notify the cvs server that you are editing the file and should change the
file attributes so that it is writable.

It is not strictly necessary to use the edit command.  You could just use
chmod to change the file permissions and then edit the file.  Either way the
commit is what causes the changes to be reflected in the repository.
However, you should use cvs edit if that is enabled.

-Mark


----- Original Message -----
From: "Y Hu" <address@hidden>
To: "Mark Priest" <address@hidden>; <address@hidden>
Sent: Friday, August 01, 2003 12:30 AM
Subject: Re: checkout


> Thanks Mark.
>
> The file dummy.c is really in the server depository
> (it is not a real file name, just for example here).
>
> I know "cvs co module" works, it checks out the whole
> directory. Now, the real question is how do you check
> out a file for editing? I thought "cvs co dummy.c"
> changes a read-only file dummy.c to a read-write file
> in my local directory, so that I can edit the dummy.c
> in my local directory. If I use "cvs update dummy.c",
> it won't change the read-only attribute. What is the
> GNU cvs command to check out a file for editing?
>
> Thank you.
>
> yh
> --- Mark Priest <address@hidden> wrote:
> > 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.
> >
> > -Mark
> >
> > ----- Original Message -----
> > From: "Y Hu" <address@hidden>
> > To: <address@hidden>
> > Sent: Thursday, July 31, 2003 10:59 PM
> > Subject: Re: checkout
> >
> >
> > > Hi,
> > >
> > > 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
> > > it?
> > >
> > > Thank you.
> > >
> > > yh
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! SiteBuilder - Free, easy-to-use web site
> > design software
> > > http://sitebuilder.yahoo.com
> > >
> > >
> > > _______________________________________________
> > > Info-cvs mailing list
> > > address@hidden
> > > http://mail.gnu.org/mailman/listinfo/info-cvs
> > >
> >
> >
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com