Hi Peff, On Tue, 1 May 2012, Jeff King wrote: > On Tue, May 01, 2012 at 03:33:26AM -0400, Jeff King wrote: > > > In this case, send pack gets its arguments from the command-line, not > > from the options set at the transport layer. Remote-curl will pass along > > "--quiet" if we get that from the transport layer, but it does not > > otherwise pass along the "progress" flag. So there are two problems: > > > > 1. send-pack defaults its progress boolean to 0. Before 01fdc21, that > > was OK, because it meant "don't explicitly ask for progress". But > > after 01fdc21 that now means "explicitly ask for no progress", and > > the direct-transport code paths were updated without updating > > cmd_send_pack. > > > > 2. There's no way to tell send-pack explicitly "yes, I would like > > progress, no matter what isatty(2) says". I doubt anybody cares > > much, but it probably makes sense to handle that for the sake of > > completeness. > > The following patch series fixes this: > > [1/3]: send-pack: show progress when isatty(2) > [2/3]: teach send-pack about --[no-]progress > [3/3]: t5541: test more combinations of --progress Thanks. I applied and pushed it after testing on Linux. David, if you want to relieve me of maintenance burden in the future, you # apply the patches # push them to a fork on GitHub # run the tests # report back to the mailing list (including the outcome of the test -- detailed, if it fails) Ciao, Johannes -- 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