Stephen Boyd <bebarino@xxxxxxxxx> writes: > I am not sure why "current branch $branch is up to date" and > "Fast-forwarded $branch to $onto" is echoed to stderr, but I've > wrapped those in a quiet check because it doesn't seem to be > an error. Maybe those should be changed to stdout? There are many valid cases where it makes sense to use stderr for messages that are not errors (e.g. diagnostics, prompts, progress reports, and informational messages that otherwise would clutter machine parsable output meant to go to stdout). I do not understand why some people seem to think stderr is only for errors. I think we even saw a broken interpretive language environment where the system considers it an error if a program it launched said anything to stderr, instead of correctly diagnosing the exit status from it? It is a disease. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html