From: Junio C Hamano <gitster@pobox.com>
To: Sayooj Surendran <sayooj.surendran@bigbinary.com>
Cc: git@vger.kernel.org
Subject: Re: Output of git checkout goes to stderr
Date: Tue, 30 Jul 2024 08:45:36 -0700 [thread overview]
Message-ID: <xmqqed7ag9y7.fsf@gitster.g> (raw)
In-Reply-To: <CAFGW38fkr+OuhpcyqNFxZNkhNDGPxTbOmCJLVHpCGUmbj05tMg@mail.gmail.com> (Sayooj Surendran's message of "Tue, 30 Jul 2024 11:14:18 +0530")
Sayooj Surendran <sayooj.surendran@bigbinary.com> writes:
> Noticed that the output of git checkout command is going to stderr
> channel. Is this an intended behaviour?
Show messages meant for human consumptions (not just errors and
warnings, but informational messages and eye-candy progress bars) to
the standard error stream, and using the standard output stream to
show what informational commands are asked to produce (e.g. running
"git status" would describe the status of the current working tree
to the standard output stream), is very much in line with the
original design we laid out in 2005 when Git was still very young,
and continues to be "intended" behaviour to this day.
prev parent reply other threads:[~2024-07-30 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 5:44 Output of git checkout goes to stderr Sayooj Surendran
2024-07-30 7:36 ` Eric Sunshine
2024-07-30 7:46 ` Karthik Nayak
2024-07-30 15:45 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqed7ag9y7.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sayooj.surendran@bigbinary.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).