Re: cvs edit/commit problem

[Noel L Yap]

address@hidden on 2000.10.05 13:25:57
>On Thu, 5 Oct 2000, Richard J. Duncan wrote:
>>
>> Is this a know bug in CVS? Is there a known workaround? Maybe some
>
>No it is not a bug.  If CVS did this it would be a bad idea  for the same
>reason that the directive to automatically unedit the file you suggested
>would be a bad idea.  The known work around it to either:
>
>* only edit what you intend to edit (rather than cvs edit *)
>* explicitly unedit everything you edit
>
>I would suggest a combination.  Edit only what you need and unedit
>everything you've edited explicitly.  Editing everything in a directory
>may be convient for the person working on the files, but what if a second
>person wants to work on something the first person doesn't even intend to
>touch?

I agree.

>  The second person must wait until the first has released his/her
>edit for a file they weren't even using.

This isn't true.  Unless the team is using the "cvs edit -c" patch, nothing
prevents multiple edits on a file.

>    So my first suggestion would be to use this routine:
>
>1) cvs edit <specific files>
>2) vi <files>
>3) cvs commit <files>

Yes.

>But if you must do a global edit * then:
>
>1) cvs edit *
>2) vi <file1, ...>
>3) cvs unedit *
>4) cvs commit

Yes.  It should also be noted that "cvs unedit" (rather than "cvs unedit *") is
sufficient, but not necessary, to do the job.  "cvs unedit", like "cvs ci" will
recursively traverse the working directory structure.

>This way the programer explicitly releases those files.  You could even
>make a simple shell script that did those last two commands together.

It just occurred to me that developers may "cvs edit *" in order to watch
everything.  If this is the case, then it would be better to use "cvs watch add
*" than "cvs edit *".

Noel



This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.