Re: stdout versus stderr for cmd line git

Hi, Michael Hunley wrote: > Ok, we can filter that out. But worse is that actual errors in a pull > request are sent to stdout instead of standard error. For example, > merge conflicts or pull failures because you have unstaged changes. Yes, errors and progress output should go to stderr. The

stdout versus stderr for cmd line git

I have been building some automated patching scripts to update multiple servers at once from our dev host. In doing so I ran into some oddities with linux command line GIT version 1.8.0-rc0, so a couple minor revisions behind. First, a "git pull" puts the list of branches updated onto stderr. The