Thread (3 messages) flat view 3 messages, 2 authors, 2016-06-15

Re: [RFC][PATCH] Print the usage string on stdout instead of stderr.

From: Michael J Gruber <hidden>
Date: 2016-06-15 22:48:49

Miles Bader venit, vidit, dixit 17.05.2010 14:07:
Michael J Gruber [off-list ref] writes:
quoted
Now, usage messages are displayed on specific request (-h) as well as
when a command is used with wrong arguments. So the classification
depends on the use case! But I reckon that even with '-h', usage strings
are not exactly "regular output", so stderr looks more natural to me.
Usage info specifically requested by the user is not error output, it is
the output of the command.  It should be output to stdout, not stderr.
Well sure it is, just as I wrote. So do you suggest that the file handle
should depend on the use case? Care to implement?
[Note that for GNU progs, this behavior is explicitly required by the
GNU coding standards, and I think it's a pretty reasonable rule.]
Fortunately, Git is not GNU software.

Michael
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help