chiark / gitweb /
Print progress message to stderr, not stdout
authorKarl Hasselström <kha@treskal.com>
Thu, 16 Nov 2006 19:45:28 +0000 (19:45 +0000)
committerCatalin Marinas <catalin.marinas@gmail.com>
Thu, 16 Nov 2006 19:45:28 +0000 (19:45 +0000)
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.

Signed-off-by: Karl Hasselström <kha@treskal.com>
Signed-off-by: Catalin Marinas <catalin.marinas@gmail.com>
stgit/git.py

index 20cac6136e2296be9f0851440f9cfb8881691e49..0e83ffc5cceb9af88723f4e9c5664c27b9ad56df 100644 (file)
@@ -186,8 +186,9 @@ def __tree_status(files = None, tree_id = 'HEAD', unknown = False,
     """Returns a list of pairs - [status, filename]
     """
     if verbose:
-        print 'Checking for changes in the working directory...',
-        sys.stdout.flush()
+        print >> sys.stderr, \
+              'Checking for changes in the working directory...',
+        sys.stderr.flush()
 
     refresh_index()
 
@@ -226,7 +227,7 @@ def __tree_status(files = None, tree_id = 'HEAD', unknown = False,
             cache_files.append(fs)
 
     if verbose:
-        print 'done'
+        print >> sys.stderr, 'done'
 
     return cache_files