Rahul Bhargava writes:
>
> Sounds like a good idea.
Looks like I'm in the minority. Go for it, Derek.
-Larry Jones
I'm a genius. -- Calvin
___
Bug-cvs mailing list
Bug-cvs@nongnu.org
http://lists.nongnu.org/mailman/listinfo/bug-cvs
Sounds like a good idea. Cleaning up past skeletons like these
will help new users who choose CVS. Old users like me have
always been puzzled by the "P" status as it reveals implementation
details that a user shouldn't care about.
Larry Jones wrote:
Derek R. Price writes:
Only semi-gratuito
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derek R. Price wrote:
> Schrum, Allan (Allan) wrote:
>>With
>>the "-t" trace option, this can then be output as a "P" for debugging
>>purposes.
>
>
> Sure. That's a good idea.
Sounds good to me.
- --
Jim Hyslop
Dreampossible: Better software. Simp
Mark,
It works fine. Just rebuild and tested.
I had some problem with [.src]client.c
Based on your last e-mail I restored client.c to it's original state,
meaning I removed my error handling in
both handle_m and handle_e. Result check-out CVS test failed.
Error: "cvs: cannot write to stderr
Larry Jones wrote:
> Yes, it probably would have saved a lot of confusion if "P" had never
> existed. But it has, and the questions about it have mostly died down
> now. I'm afraid that getting rid of it will just cause people who were
> used to the old behavior (and people using old versions of
Derek R. Price writes:
>
> 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 seem
Schrum, Allan (Allan) wrote:
> Perhaps leave the code but change the "Patched" indicator to be "U"?
This is exactly what I meant to suggest.
> With
> the "-t" trace option, this can then be output as a "P" for debugging
> purposes.
Sure. That's a good idea.
Derek
--
Derek R. Price
CVS Solutio
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: bu
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
Hi Piet,
I am given to understand by a MacOS X (10.3.6)
user that neither the MACOS nor the TARGET_OS_MAC
macros are being defined during a normal cvs
configure and build operation which makes the
VMS_filename_classes symbol become unresolved due
to the last patch to system.h
It appears that USE_
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 i
Hey all,
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.
12 matches
Mail list logo
