From 3d9830c3ce1bcd6ea9d8efa492b24ba8523873dd Mon Sep 17 00:00:00 2001 From: Kir Kolyshkin Date: Mon, 7 Apr 2008 23:59:18 +0400 Subject: [PATCH] gitdm: Report progress to stderr not stdout When gitdm is used for generating text-only report with its output redirected to a file, all is well aside from the clutter at the beginning of that file -- a very long line with repeating "Grabbing changesets...". Solve that by redirecting progress reporting to stderr. It also helps to see the progress when you redirect gitdm output to a file. Also, we don't have to flush stdout since stderr is unbuffered by default. Signed-off-by: Kir Kolyshkin Signed-off-by: Jonathan Corbet --- gitdm | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/gitdm b/gitdm index 32f27c8..d580414 100755 --- a/gitdm +++ b/gitdm @@ -447,14 +447,12 @@ ParseOpts () # # Snarf changesets. # -print 'Grabbing changesets...\r', -sys.stdout.flush () +print >> sys.stderr, 'Grabbing changesets...\r', printcount = CSCount = 0 while (1): if (printcount % 50) == 0: - print 'Grabbing changesets...%d\r' % printcount, - sys.stdout.flush () + print >> sys.stderr, 'Grabbing changesets...%d\r' % printcount, printcount += 1 p = grabpatch() if not p: @@ -469,7 +467,7 @@ while (1): for sobemail, sob in p.sobs: sob.addsob (p) CSCount += 1 -print 'Grabbing changesets...done' +print >> sys.stderr, 'Grabbing changesets...done' if DumpDB: database.DumpDB ()