Perhaps leave the code but change the "Patched" indicator to be "U"? With the "-t" trace option, this can then be output as a "P" for debugging purposes.
-Allan -----Original Message----- From: Derek R. Price [mailto:[EMAIL PROTECTED] Sent: Monday, November 14, 2005 3:01 PM To: Larry Jones Cc: [email protected] Subject: Re: "P" status from update Larry Jones wrote: > Derek R. Price writes: > >>Would anyone be very offended if I blew away update's "P" status code in >>favor of "U"? I am of the opinion that most users would like to assume >>that CVS saved as much bandwidth as possible and could care less about >>running status about whether CVS was successful in this endeavor or not. > > > It seems like a gratuitous change to me -- I'd leave it alone. Only semi-gratuitous, and though I neglected to mention it the first time, I would only do this on feature. I've been teaching CVS training classes for the last few years, and the difference between "U" and "P" usually appears to be one of the topics where it seems student's eyes begin glazing over. I get the impression that the students that understand generally don't care and the students that haven't used diff & patch before sometimes need to be told second and subsequent times. I usually end up explaining the difference between "U" and "P" again at least once per class while I am running the students through examples after a lecture. I believe the comment from one student was, "we want to know how to use CVS, not how it works." The existance of the "P" status code at all now seems somewhat gratuitous to me. Regards, Derek -- Derek R. Price CVS Solutions Architect Ximbiot <http://ximbiot.com> v: +1 717.579.6168 f: +1 717.234.3125 <[EMAIL PROTECTED]> _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
