"Jack O'Connor" <oconnor663@xxxxxxxxx> writes: > In git 2.3.7 I could run the following command and see progress in the > terminal, despite the redirection of stdout and stderr: > > git clone https://github.com/oconnor663/dotfiles --progress 2>&1 | cat > > As of 2.4, that command no longer shows progress. When I bisect, the > responsible commit is 2879bc3b0c3acc89f0415ac0d0e3946599d9fc88 > ("transport-helper: ask the helper to set progress and verbosity > options after asking for its capabilities"). Can anyone suggest a > workaround? > > -- Jack O'Connor That commit is by Mike Hommey <mh@xxxxxxxxxxxx> so I'd imagine that CC'ing the author of the patch would be the first thing to do ;-) I am kind of surprised that the commit changes behaviour, though. If I didn't hear that you had trouble in 2.4, I would have suspected 85cb8906 (progress: no progress in background, 2015-04-13) instead. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html