Re: [PATCH] Print progress message to stderr, not stdout
- From
Karl Hasselström <kha@treskal.com>
- Date
- Dec 4, 2006, 15:37 UTC
- Message-ID
- <20061204153705.GA8644@diana.vm.bytemark.co.uk>
- In-Reply-To
- <b0943d9e0612040117y6554b891yaf6eb59d0d52ebf0@mail.gmail.com>
On 2006-12-04 09:17:16 +0000, Catalin Marinas wrote:
Show 14 quoted lines
> On 02/12/06, Marco Costalba <mcostalba@gmail.com> wrote: > > > On 11/11/06, Karl Hasselström <kha@treskal.com> 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. > > 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)?
I introduced this since I wanted to divert the output to a file, and the progress message had no business being written to that file. But a command line option to suppress progress messages would work just as well if that's what git does.
-- Karl Hasselström, kha@treskal.com