diff options
| author | Luke Shumaker <lukeshu@datawire.io> | 2021-04-27 15:17:42 -0600 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2021-04-28 16:47:18 +0900 |
| commit | 534ff90dbd74a81beee357220cfa026efc18fea6 (patch) | |
| tree | a34fb1e4d3e7ee501ac0d1b3e2ee5cac895d2181 /builtin/commit.c | |
| parent | subtree: add comments and sanity checks (diff) | |
| download | git-534ff90dbd74a81beee357220cfa026efc18fea6.tar.gz git-534ff90dbd74a81beee357220cfa026efc18fea6.zip | |
subtree: don't let debug and progress output clash
Currently, debug output (triggered by passing '-d') and progress output
stomp on each other. The debug output is just streamed as lines to
stderr, and the progress output is sent to stderr as '%s\r'. When
writing to a file, it is awkward to read and difficult to distinguish
between the debug output and a progress line. When writing to a
terminal the debug lines hide progress lines.
So, when '-d' has been passed, spit out progress as 'progress: %s\n',
instead of as '%s\r', so that it can be detected, and so that the debug
lines don't overwrite the progress when written to a terminal.
Signed-off-by: Luke Shumaker <lukeshu@datawire.io>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/commit.c')
0 files changed, 0 insertions, 0 deletions