From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH] Print progress message to stderr, not stdout
Date: Sat, 11 Nov 2006 13:16:25 +0100 [thread overview]
Message-ID: <20061111121625.8988.45195.stgit@localhost> (raw)
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>
---
I noticed this when creating a patch with "stg export -s" for the
import regression test.
stgit/git.py | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/stgit/git.py b/stgit/git.py
index 2a6ae91..8d88769 100644
--- a/stgit/git.py
+++ b/stgit/git.py
@@ -186,8 +186,8 @@ def __tree_status(files = None, tree_id
"""Returns a list of pairs - [status, filename]
"""
if verbose:
- print 'Checking for changes in the working directory...',
- sys.stdout.flush()
+ sys.stderr.write('Checking for changes in the working directory...')
+ sys.stderr.flush()
refresh_index()
@@ -226,7 +226,7 @@ def __tree_status(files = None, tree_id
cache_files.append(fs)
if verbose:
- print 'done'
+ print >> sys.stderr, 'done'
return cache_files
next reply other threads:[~2006-11-11 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 12:16 Karl Hasselström [this message]
2006-12-02 13:20 ` [PATCH] Print progress message to stderr, not stdout Marco Costalba
2006-12-04 9:17 ` Catalin Marinas
2006-12-04 15:37 ` Karl Hasselström
2006-12-04 18:34 ` Marco Costalba
2006-12-04 22:13 ` Catalin Marinas
2006-12-05 6:11 ` Marco Costalba
2006-12-05 7:41 ` Johannes Schindelin
2006-12-05 9:06 ` Karl Hasselström
2006-12-05 9:06 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061111121625.8988.45195.stgit@localhost \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).