From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: is anyone getting pathetic git download from the new kmod SRC_URI?
Date: Tue, 20 Nov 2012 14:14:31 -0700 [thread overview]
Message-ID: <50ABF2B7.8060006@mlbassoc.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1211201605110.30424@oneiric>
On 2012-11-20 14:08, Robert P. J. Day wrote:
> On Tue, 20 Nov 2012, Tom Zanussi wrote:
>
>> On Tue, 2012-11-20 at 15:27 -0500, Robert P. J. Day wrote:
>>> maybe it's something i'm doing, but oe-core just changed the SRC_URI
>>> for kmod to git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git,
>>> and the response from the URL couldn't suck any worse than if it
>>> sucked totally. i've yet to get a successful clone.
>>>
>>> thoughts? is that working fine for others?
>>>
>>
>> No problems here:
>>
>> [trz@empanada tmp]$ time git clone git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git
>> Cloning into 'kmod'...
>> remote: Counting objects: 4003, done.
>> remote: Compressing objects: 100% (1599/1599), done.
>> remote: Total 4003 (delta 2811), reused 3196 (delta 2264)
>> Receiving objects: 100% (4003/4003), 4.59 MiB | 850 KiB/s, done.
>> Resolving deltas: 100% (2811/2811), done.
>>
>> real 0m7.183s
>> user 0m0.361s
>> sys 0m0.429s
>
> i can't explain it -- i've yet to have a successful clone from that
> URL. hangs partway through every time.
Maybe it's a routing thing - where are you located?
n.b. it just worked for me - in about the same <10 seconds
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-11-20 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 20:27 is anyone getting pathetic git download from the new kmod SRC_URI? Robert P. J. Day
2012-11-20 21:02 ` Tom Zanussi
2012-11-20 21:08 ` Robert P. J. Day
2012-11-20 21:14 ` Gary Thomas [this message]
2012-11-20 21:30 ` Robert P. J. Day
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=50ABF2B7.8060006@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.