From: "Aubrey Li" <aubreylee@gmail.com>
To: git@vger.kernel.org
Subject: git clone problem
Date: Tue, 3 Apr 2007 13:56:13 +0800 [thread overview]
Message-ID: <6d6a94c50704022256t305c964eq45cc4189dcf20c27@mail.gmail.com> (raw)
Somehow I can't clone a git repository any more through http, which I
can do it before. Git clone always hangs at the same commit-ID,
without any error, warnings.
Please help, thanks.
Best Regards,
-Aubrey
=============================================
aubrey@ubuntu-feisty:~/upstream-uboot$ git-clone
http://www.denx.de/git/u-boot-blackfin.git
----snip----
walk d2c83f549378fb3fc34cb3c2e62fd772fbf8b68b
got b2e8b3c69774357044f39186a10cf1542bde6be5
got 2da827b326038662feb6f28cb0f9a3d86cef6b2e
got f9741f4fc9f4b1165c58d76dc58e0593808b84e5
got eb62a0abe8bdea88c563380c302a88fa64eff151
got 620d3c9a14affca29a5c4e575e9f355c2bd4aed2
got 58e3b14c18ed3288ceef8d086946dbf3df64ccf2
got 0612ed5872dbec0736e779eb28748af04c0d4f1c
walk 620d3c9a14affca29a5c4e575e9f355c2bd4aed2
walk 4decd84e8f04279c5cfff7f8e907465ef8d8a3fb
walk 58e3b14c18ed3288ceef8d086946dbf3df64ccf2
walk e59581c56ab5d6e0207ddac3b2c1d55cb36ec706
walk dae80f3caf9754a6dd3ddf3cf903d0c46cbd4385
walk e4c2d37adc8bb1bf69dcf600cbc6c75f916a6120
walk 1954be6e9c9421b45d0a9d05b10356acc7563150
walk fae684e89844856383bdf101440889557df3e6b1
walk 4e26f1074c3ac1bd8fd094f0dc4a1c4a0b15a592
walk 1aa934c81b77f2080d3ca4b226eab67b17a33961
walk 4f4b602ec7524a032bdf3c6d28c7f525a4a67eaa
walk 1729b92cde575476684bffe819d0b7791b57bff2
got 3ab1a99fbc6527441b6932b20d3e0a262a9d5fdb
got a6c834c3ece23487b4f744bfc516c78aab800117
got 4be23a12f23f1372634edc3215137b09768b7949
--------hang here--------
next reply other threads:[~2007-04-03 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 5:56 Aubrey Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-28 23:08 git clone problem Steven Sroka
2017-01-25 16:58 Jordi Durban
2017-01-25 17:58 ` Santiago Torres
2017-01-27 9:18 ` Jordi Durban
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=6d6a94c50704022256t305c964eq45cc4189dcf20c27@mail.gmail.com \
--to=aubreylee@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).