When we receive a large push, the server side of the connection may spend a lot of time (30s or more for a full push of linux.git) walking the object graph without producing any output. Let's give the user some indication that we're actually working. Signed-off-by: Jeff King <peff@xxxxxxxx> --- builtin/receive-pack.c | 1 + 1 file changed, 1 insertion(+) diff --git a/builtin/receive-pack.c b/builtin/receive-pack.c index d309109..7db1639 100644 --- a/builtin/receive-pack.c +++ b/builtin/receive-pack.c @@ -1342,6 +1342,7 @@ static void execute_commands(struct command *commands, data.cmds = commands; data.si = si; opt.err_fd = err_fd; + opt.progress = err_fd && !quiet; if (check_connected(iterate_receive_command_list, &data, &opt)) set_connectivity_errors(commands, si); -- 2.9.1.434.g748be50 -- 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