[EMAIL PROTECTED] on 2000.07.21 03:02:56
>> > I don't quite see the point in having edit watches if they
>> >can be defeated like this but they can also be defeated by using
>> >chmod.
>
>I couldn't agree more. Of course you can use chmod or other trics to
>defeat the system in any case. The important thing is that an unedit
>that does not revert makes it possible to committ the edited file by
>accident if the developer forgets to revert the file manually. There is
>a very significant differenct between a tool and user interface design
>that can be overridden by a skilled user, and a design that makes these
>kinds of accidents possible.
Then don't use CVS (which you're not, you're using WinCVS -- a wrapper). By
default, the following is possible:
cvs co module # all files are checked out read-write
cd module
echo hello >>file # assuming file already exists
cvs ci
WinCVS hides this behaviour from you. It can also hide the non-modifying "cvs
unedit" from you.
>> Exactly. "cvs edit" and family are meant to /facilitate/ communication.
>> They're not meant to enforce communication. For example, I habitually chmod
>> when all I want to do is add a debug printf. If later I find that I really
want
>> to commit the file in the future, I'll "cvs edit" it.
>
>I my mind, a good version control system should always enforce
>consitency and safety by default (but let you break the rules if when
>have to). The described edit/unedit behaviour seems to follow the
>opposite philosophy: Do it right if you want to... I really don't think
>that is a good idea. Others might dissagree.
Obviously, I disagree ;) Or, at least, I disagree what "right" is in this
circumstance.
CVS doesn't enforce any policy. If you want to enforce policy, wrap CVS.
>I might check in RCVS later to see in which direction things are going,
>but I'll think leave you alone for now. Things seem to be going in the
>wrong direction here at the moment.
Again, we disagree on what "right" and "wrong" are.
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.
