On 02/12/06, Marco Costalba <mcostalba@xxxxxxxxx> wrote:
On 11/11/06, Karl Hasselström <kha@xxxxxxxxxxx> wrote: > Printing progress messages to stdout causes them to get mixed up with > the actual output of the program. Using stderr is much better, since > the user can then redirect the two components separately. This patch breaks qgit. GUI interface to stgit pop and push commands is broken because a command that prints to stderr is considered a failing one by qgit. I would kindly ask you to: 1 - Revert the patch. That would be the best. You can use a prefix to printed message instead, see git pull, something like 'stg: bla bla bla' . In any case, IMHO, using stderr for normal activity logging does not sound like a great idea in general. 2 - At least add a '-v' '--verbose' option that defaults to quiet so to not break back compatibility.
Since there are other tools relying on a clean stderr, I think I would revert it and add a verbose flag and/or config option. Karl, any thoughts on this (since you sent the patch)? -- Catalin - 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