{"thread":{"id":"27504","subject":"Re: Non-error messages appears in STDERR","startedAt":"2011-05-30T20:29:42Z","lastAt":"2011-05-30T20:29:42Z","messageCount":1,"participants":["Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"169026","messageId":"20110530202942.GA14913@elie","threadId":"27504","inReplyTo":"86adad09-bba9-4415-834c-c004071fd9c2@l14g2000pro.googlegroups.com","subject":"Re: Non-error messages appears in STDERR","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2011-05-30T20:29:42Z","receivedAt":"2011-05-30T20:29:42Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nPok Man Lau wrote:\n\n> I am writing a class library to wrap bin\\git.exe and trying to be a\n> bit more accurate on error handling. Here are something interesting I\n> found so far with git version 1.7.2.3.msysgit.0\n>\n> Some of the command output returned by git.exe appeared to be STDERR\n> instead of STDOUT even they are not error message.\n>\n> For example:\n> checkout <branch_name>\n>\n> I would expected the message \"Switched to branch '<branch_name>'\" to\n> be a STDOUT, but it appears to be STDERR.\n\nYes, generally speaking the intent is the \"result\" or output that\ncould be conceivably parsed will go to stdout, while progress\ninformation goes to stderr.\n\nI think it would make sense to document this somewhere, e.g., in the\n\"git help cli\" text.  Do you think that's the right place?  Any ideas\nfor wording?\n\nThanks much,\nJonathan\n"}]}