From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] git clone problem
Date: Tue, 03 Apr 2007 12:47:38 +0200 [thread overview]
Message-ID: <m2r6r1rayd.fsf@sowhat.denx.de> (raw)
In-Reply-To: <27d85ee10704022052s19450326i41a36b5ac1f3508d@mail.gmail.com> (Aubrey Li's message of "Tue\, 3 Apr 2007 11\:52\:31 +0800")
Hi Aubrey,
> Somehow I can't clone my git repository any more, git-clone always
> hangs at the same commit-ID as follows.
> Please help, thanks.
>
> Best Regards,
> -Aubrey
>
> aubrey at 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
Hm. Can't you use the git:// protocol? This is much more efficient
anyway and whats more, I just tried and this works
like a charm.
I also tried the http:// method and admittedly it hung on first try -
using git 1.4.4.1. I checked and it looks like git-http-pull might
have a problem there (the last objected from your list actually
produces a 404 not found on our server). I upgraded my local git to
1.5.0.3 and now it works.
Can you please try using the git protocol or otherwise updateing your
git version?
Thanks
Detlev
--
FORTRAN's tragic fate has been its wide acceptance, mentally chaining thousands
and thousands of programmers to our past mistakes. I pray daily that more of my
fellow-programmers may find the means of freeing themselves from the curse of
compatibility. -- Edsger W. Dijkstra
--
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany +49 8142 66989 40
next prev parent reply other threads:[~2007-04-03 10:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 3:52 [U-Boot-Users] git clone problem Aubrey Li
2007-04-03 10:13 ` Robert Fitzsimons
2007-04-03 10:34 ` Aubrey Li
2007-04-03 10:47 ` Detlev Zundel [this message]
2007-04-03 12:54 ` Wolfgang Denk
2007-04-05 6:35 ` Aubrey Li
2007-04-05 8:13 ` Mike Frysinger
2007-04-05 8:34 ` Aubrey Li
2007-04-05 14:15 ` Sam Song
2007-04-03 10:56 ` Peter Pearse
2007-04-03 12:41 ` Wolfgang Denk
2007-04-05 7:29 ` Aubrey Li
2007-04-03 14:37 ` Timur Tabi
2007-04-05 7:31 ` Aubrey Li
2007-04-05 16:59 ` Scott Wood
2007-04-04 0:48 ` Mike Frysinger
2007-04-05 7:34 ` Aubrey Li
2007-04-05 8:11 ` Mike Frysinger
2007-04-05 9:18 ` Wolfgang Denk
2007-04-05 7:16 ` Zang Roy-r61911
2007-04-05 12:17 ` Aubrey Li
2007-04-06 0:40 ` Zang Roy-r61911
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=m2r6r1rayd.fsf@sowhat.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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