Re: cvs abusing stderr?

[gnu-cvs]

> but I am sure that it can
> read from cvs' stdout instead of stderr, too.

Yes, it *could*. But at the moment it expects this particular input from 
stderr and all (?) other versions of CVS servers send it at stderr. 
There are already too much differences between GNU CVS and CVSNT...

> Wouldn't it be more consistent to reserve stderr for
> error messages, and to write log messages to stdout,
> as usual?

It would be more consistent, if the client-server protocol (and this is 
what we are talking about) would send the information in a unambiguous 
format and translate it *at client side* in human readable text. 
Unfortunately, the CVS server already converts it to human readable 
format and the more advanced clients need to parse it, which is not 
possible correctly in all cases (e.g. imagine file names with spaces and 
the output of the 'cvs history' command).

--
Best regards
Thomas Singer
_____________
smartcvs.com


Harald Dunkel wrote:
> gnu-cvs@regnis.de wrote:
>
> > Just to prevent an out-of-the-brain change: if they would we sent to
> > stdout, this would break at least SmartCVS.
>
>
> I don't want to break your GUI, but I am sure that it can
> read from cvs' stdout instead of stderr, too.
>
> Wouldn't it be more consistent to reserve stderr for
> error messages, and to write log messages to stdout,
> as usual?
>
>
> Regards
>
> Harri