Noel Yap wrote:
>
>[EMAIL PROTECTED] on 2000.07.20 12:52:32
>>>>If it doesn't "unmodify" code, what is its purpose, then?
>>>
>>>Exactly what the command is, "cvs unedit". It removes the edit
from
>>the file
>>>and notifies watchers of the action. I forget how I had it treat
the
>>write bit
>>>(in my patch).
>>>
>>>Remember, "cvs edit" and family are there to facilitate
communication
>>>among developers. Nothing else.
>>
>>So, what happens when you try and commit that module. Will it
commit
>>that file or not?
>
>Yes, this behaviour is consistent with OOTB CVS (ie without "cvs
edit"). For
>example:
>cvs co module
>cd module
>cat hello >> file # OOTB CVS has files read-write
What does OOTB mean?
>cvs ci # will checkin file
>
>If you don't want this behaviour, use the "cvs ci -c" patch which'll
check for
>valid edits before committing.
>
So, if I understand you correctly, I can "cvs unedit" a file which
will still leave it in its modified state and then check it in. I
assume that the watchers will get the "commit" notification but they
won't get the "edit" notification because the developer has used
"unedit". 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.
Personally, I would like to see some sort of module "revert" command.
Currently, I can only revert a file at a time by doing:
rm file
cvs update file
Conceivably, I could write a script or an alias to do this recursively
for every sub-module but I would prefer that cvs supported it "out of
the box". To me, the meaning of "unedit" is the ideal command to do
this. So all I would do is:
cvs unedit module
and it would revert all my changes in module and all its sub-modules.
--
Stephen Rasku E-mail: [EMAIL PROTECTED]
Senior Software Engineer Web: http://www.tgivan.com/
TGI Technologies http://www.pop-star.net/
