From: Jim Meyering <jim@meyering.net>
To: git list <git@vger.kernel.org>
Subject: "git clone --depth=2 git://git.sv.gnu.org/gnulib" hangs
Date: Mon, 25 Apr 2011 22:28:10 +0200 [thread overview]
Message-ID: <87aafedqjp.fsf@rho.meyering.net> (raw)
Hello,
We've had a report that this command is hanging:
git clone --depth=2 git://git.sv.gnu.org/gnulib
cloning without --depth=N works, as well as when using an ssh:// URL,
but most people can use ssh:// URLs.
Normally it wouldn't be much of a problem, but many projects
use gnulib as a submodule, and one of the recommended (scripted)
ways to get a copy is via a shallow clone.
savannah's server is running git-1.7.2.5.
I've confirmed it using these client versions:
1.7.5.rc3.316.gd1ff9
1.7.4.4
GIT_TRACE didn't give much info:
xx$ GIT_TRACE=1 git clone --depth 2 git://git.sv.gnu.org/gnulib
trace: built-in: git 'clone' '--depth' '2' 'git://git.sv.gnu.org/gnulib'
Cloning into gnulib...
trace: run_command: 'index-pack' '--stdin' '-v' '--fix-thin' \
'--keep=fetch-pack 645 on xx.meyering.net'
trace: exec: 'git' 'index-pack' '--stdin' '-v' '--fix-thin' \
'--keep=fetch-pack 645 on xx.meyering.net'
trace: built-in: git 'index-pack' '--stdin' '-v' '--fix-thin' \
'--keep=fetch-pack 645 on xx.meyering.net'
It appears to be something specific to the gnulib repository,
since I can do a shallow clone of e.g., this one just fine:
git://git.savannah.gnu.org/parallel.git
Any hints?
At worst I'll set up a git server on a private system and debug it --
eventually.
Regards,
Jim
next reply other threads:[~2011-04-25 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 20:28 Jim Meyering [this message]
2011-04-25 21:16 ` "git clone --depth=2 git://git.sv.gnu.org/gnulib" hangs Andreas Schwab
2011-04-26 7:59 ` Jeff King
2011-04-26 16:02 ` Jim Meyering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aafedqjp.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.