| commit | 7655b4119d49844e6ebc62da571e5f18528dbde8 | |
| author | René Scharfe <l.s.r@web.de> | |
| Tue, 3 Mar 2020 20:55:34 +0000 (3 21:55 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 3 Mar 2020 21:15:40 +0000 (3 13:15 -0800) | ||
| tree | eda6264cd28cf2439f8982708b2f46a22564b5e6 | treesnapshot (tar.gz zip) |
| parent | d0654dc308b0ba76dd8ed7bbb33c8d8f7aacd783 | commitdiff |
remote-curl: show progress for fetches over dumb HTTP
Fetching over dumb HTTP transport doesn't show any progress, even with
the option --progress. If the connection is slow or there is a lot of
data to get then this can take a long time while the user is left to
wonder if git got stuck.
We don't know the number of objects to fetch at the outset, but we can
count the ones we got. Show an open-ended progress indicator based on
that number if the user asked for it.
Signed-off-by: René Scharfe <l.s.r@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Fetching over dumb HTTP transport doesn't show any progress, even with
the option --progress. If the connection is slow or there is a lot of
data to get then this can take a long time while the user is left to
wonder if git got stuck.
We don't know the number of objects to fetch at the outset, but we can
count the ones we got. Show an open-ended progress indicator based on
that number if the user asked for it.
Signed-off-by: René Scharfe <l.s.r@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| remote-curl.c | diffblobblamehistory | |
| walker.c | diffblobblamehistory | |
| walker.h | diffblobblamehistory |