[Top][All Lists]

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

Re: cvs edit/commit problem

From: Richard J. Duncan
Subject: Re: cvs edit/commit problem
Date: Thu, 5 Oct 2000 13:28:01 -0500 (CDT)

> 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 want to
edit it so I type "cvs edit <file1>" Then with further investigation I
see the problem is really in file2, so I do "cvs edit <file2>" and
then make my changes in file2. Then I am done with editing all files
in this directory and am ready to checkin, so I do "cvs commit"

Why does cvs unedit the file that was modified and not unedit the file
that was not modified. Doesn't this part of the interface seem brain
damaged to anyone else? Either change all the files or none of the
files, but this half-baked attempt at unediting some files just leads
to problems.


reply via email to

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