> On Mon, Oct 23, 2000 at 14:59 -0500, Giang, Richard P wrote:
> >
> > Does anyone know how to enter a log message that expands
> > multiple lines using command line cvs commit -m?
>
> Does anyone know a method how to incorporate "cvs diff" into the
> "cvs commit" message and thus aid the commit
> > Is there a way to specify files not to be checked out? In other words, is
> > there a way to tell the "cvs co" command that I do not want to checkout
> > certain files?
>
> Not directly, though you could ask it to check out a file at a time. You can
> do some of that kind of thing with the
> So here's the question I have... what do we do for our working web
> directory? Is the "proper" way to do that:
> import it into CVS
> delete the current htdocs directory
> check a copy out of CVS, into the apache directory (and run from that)
>
> And then whenever there are updates, just do
> main
> main/module1
> main/module2
> ...
> main/src
> main/src/module5
> main/src/module6
> ...
>
> where main is the main module (which contains a src sub-directory),
> which happens to be on a branch other than the module* modules.
>
> When I want to update `main' onto yet another branch, I
> Is there any way to tell CVS that I want to
> add only new files to the repository? Perhaps if
> I "cvs diff $file" and check the error level for
> each file?
One easy way is to run `cvs status ` and grep for "Status:
Unknown." Pipes don't work well in a find command, so I generally
write a qui
> > >Why does cvs unedit the file that was modified and not
> > unedit the file
> > >that was not modified.
>
> Take this situation: I see problems in file1 and file2, so I "cvs edit file1
> file2".
> I fix file1 and "cvs commit".
> Why should cvs unedit file2? I still want to make changes to fi
> The purpose of "cvs edit" is to communicate to others that you
> intend to modify and commit a file. Therefore, unless you really do
> intend to modify and commit all files, "cvs edit *" is the wrong
> thing to do. Don't do that.
Ok, then take this situation. I see a problem in this file. I w
I'm experiencing a problem with cvs edit and commit. First of all, we
have a watch on the entire repository and everyone has the CVSREAD
variable set so that checkouts come as read only. This forces all
developers to use "cvs edit" before editing a file. It is common
practice, however, to just do
> Does the CVS repository keep any kind of track of who has checked out? If
> it does where does it store this information?
It depends, did you set a watch?
Read pages 27 in the Cederqvist CVS manual, then section 6.6. We add a
watch to the entire source tree. Then when people checkout code the
