Follow-up Comment #5, bug #19528 (project cvs):
After much more extensive checking, I don't believe this ever worked as
described in the manual. Files with conflicts never reach the point in the
code where the -C flag operates.
The cmd sent to the server returns with a non-zero error code (when there is
a conflict) and the update() function returns before ever getting to the point
where it checks for an overwrite selection.
This behaviour also seems to have been replicated in OpenCVS (in order to
retain compatibility I guess)
The best "fix" at this point would probably be to update the documentation
for the -C option for cvs update.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?19528>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Bug-cvs mailing list
Bug-cvs@nongnu.org
http://lists.nongnu.org/mailman/listinfo/bug-cvs
