I saw here many questions covering git and proxy topics but none of them solves my problem. I am cloning a git repository from Bitbucket. Everything works fine from my home
Two things (April 2019, seven years later):
Don't declare the NTML proxy URL directly. Set HTTP_PROXY and HTTPS_PROXY environment variables to and HTTP proxy (not an NTLM one) with, for instance, genotrance/px.
By running px (which redirects to your NTLM proxy), you can refers to a classic HTTP proxy (typically http://localhost:3128, no need for your login/password!), and this will work better.
If the "Resolving deltas" still takes time, make sure to use Git 2.22 (Q2 2019)
On that second point: A progress indicator has been added to the "index-pack" step, which often makes users wait for completion during "git clone".
See commit 79e3aa6 (31 Mar 2019) by SZEDER Gábor (szeder).
(Merged by Junio C Hamano -- gitster -- in commit da924b5, 25 Apr 2019)
index-pack: show progress while checking objectsWhen '
git index-pack' is run by 'git clone', itscheck_objects()function usually doesn't take long enough to be a concern, but I just run into a situation where it took about a minute or so: I inadvertently put some memory pressure on my tiny laptop while cloninglinux.git, and then there was quite a long silence between the "Resolving deltas" and "Checking connectivity" progress bars.Show a progress bar during the loop of
check_objects()to let the user know that something is still going on.