Junio C Hamano wrote: > There are many valid cases where it makes sense to use stderr for messages > that are not errors (e.g. diagnostics, prompts, progress reports, and > informational messages that otherwise would clutter machine parsable > output meant to go to stdout). > > I do not understand why some people seem to think stderr is only for > errors. I think we even saw a broken interpretive language environment > where the system considers it an error if a program it launched said > anything to stderr, instead of correctly diagnosing the exit status from > it? > > It is a disease. > If I understand you correctly, wrapping them in quiet checks is fine. Also, thanks for the explanation. I'll consider my self inoculated. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html