Hi 

"It's complicated"..

The devs do tend to consider which messages go to which file descriptor, 
however there is a lot of "careful" discussion about backward compatibilities 
and expectations and conflicts (between messages sharing fd's) that make it a 
bit of a lottery.

It can also be an issue between active output (required output of a command), 
passive output (background info), and true error output, with the middle case 
yo-yoing between fd 1 & 2 depending on the primary raison d'etre or the 
command..

I guess this one is lost in the mists of time (or just look back to say release 
1, see if it was like that back then, and then look at the mailing list 
archives around that time, orvthe time of any change)

Philip
  ----- Original Message ----- 
  From: tolsk...@gmail.com 
  To: Git for human beings 
  Sent: Monday, August 01, 2016 11:58 AM
  Subject: [git-users] Why does git show a part of checkout logs through stderr?


  Hi, I'm studying git for own project and I wonder why git shows some messages 
using stderr. For example, if you checkout from a to master git shows '(1) 
switched to branch master, (2) Your branch is up-to-date with "origin/master".' 
I have found (1) is through stderr and (2) is stdout. Another example is "git 
checkout <tag>", which git warns about 'detached HEAD'. It shows the message 
using stderr, but I think this is not an error. These are not critical or even 
not bugs, but I'm just curious why these logs are using stderr even they are 
not errors.

  Thanks.


  -- 
  You received this message because you are subscribed to the Google Groups 
"Git for human beings" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to git-users+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to