Thanks for the clarification. Some context. https://github.com/gitextensions/gitextensions/issues/9643 which is a side effect of https://github.com/gitextensions/gitextensions/pull/9562 So I just wanted to get some clarification on when err vs std should be used to eliminate confusion. On Wed, Mar 8, 2023 at 7:02 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Jay Asbury <vbjay.net@xxxxxxxxx> writes: > > > I see things like git fetch and other processing writing details to > > stderr and not std. > > I assume you meant "not to standard output". > > As a rule of thumb, the core of the output, the information the > end-user asked for, is sent to the standard output, whether it is > machine parseable or otherwise. And other stuff like progress > meter, warning and advice messages, are sent to the standard error. > > This should be documented already in Documentation/CodingGuidelines > for our developers. Do you think it needs to be documented for > end-users? I suspect that rather than such "principle", they are > more interested in seeing what message can be squelched with --quiet > and what can be piped to downstream with "git foo |" on case-by-case > basis individually. > > > -- Jay Asbury PC Repair and custom programs $30/hr 1hr min My Biking Blog
