Also, performing a git clone or git pull is significantly different than
downloading a tarball. Someone correct me if I am wrong but Git essentially has
to reconstruct the files from its internal data structures. If you clone a
large repository with a lot of history it will take longer than a
use GIT_CURL_VERBOSE=1 GIT_TRACE=1 git will print out full
trace. you can also try other environment variables from
https://git-scm.com/book/tr/v2/Git-Internals-Environment-Variables
In my experiences, this is usually caused by MTU discovery issue.
On Thu, Feb 23, 2017 at 7:40 AM, Bob Evans
If they are using 'git pull', or 'git push' for example, they may be
accessing the data via HTTPS or SSH.
Can your user do a 'git remote -v' and see if they are connecting via
HTTPS or SSH to assist you with troubleshooting?
Then see if it's something specific to one or the other and if it's
3 matches
Mail list logo
