[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: problem commiting file to CVSROOT

From: Daniels, Dave F [PCS]
Subject: RE: problem commiting file to CVSROOT
Date: Fri, 1 Nov 2002 09:28:32 -0600

I am not new to CVS. When I say 'users', I mean future administrators who
may not be aware there's a problem. I'm familiar with the sections you
referenced, but my problem is not addressed there (or anywhere else I can
find.) I'm not talking about normal source files, I'm talking about
administration scripts used to send email notifications. The checkoutlist
issue may be a red herring, for all I know, but it seemed odd. I'm trying to
understand why the cvs server created a ,v file but not a normal file for
certain files I checked into CVSROOT as an administrator but had no problem
with other files.


> -----Original Message-----
> From: Todd Denniston [mailto:address@hidden
> Sent: Friday, November 01, 2002 9:20 AM
> To: Daniels, Dave F [PCS]
> Cc: address@hidden
> Subject: Re: problem commiting file to CVSROOT
> "Daniels, Dave F [PCS]" wrote:
> > 
> > I have several files I'm trying to commit to a subdirectory 
> of CVSROOT, but
> > only the ,v file is being created. I'm concerened about 
> this because some
> > users may make changes without realizing the files aren't 
> being updated
> > correctly on the server. To work around this problem 
> temporarily, I've
> > manually created the necessary files on the server, but I'd like to
> > understand why this isn't being done by cvs.
> > 
> if you are talking about files in $CVSROOT/CVSROOT/ (admin files)
> then you are probably looking for:
> In this case I have to ask, Why are USERS changing any thing in this
> directory?  The users question is why I am confused as to 
> what you are asking.
> if you are new to cvs, I am concerned you are talking about 
> normal files
> (source code)?
> here I would suggest reading most of the manual
> but in particular
> and
> -- 
> I'd crawl over an acre of 'Visual This++' and 'Integrated Development
> That' to get to gcc, Emacs, and gdb.  Thank you.
>         -- Vance Petree, Virginia Power

reply via email to

[Prev in Thread] Current Thread [Next in Thread]