From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] git http access broken ?
Date: Thu, 05 Sep 2013 11:32:42 +0200 [thread overview]
Message-ID: <52284FBA.5000400@lucaceresoli.net> (raw)
In-Reply-To: <871u534o2m.fsf@dell.be.48ers.dk>
Peter Korsgaard wrote:
>>>>>> "Nicolas" == Nicolas Aguirre <aguirre.nicolas@gmail.com> writes:
> Nicolas> Hi,
> Nicolas> I'm using the git http protocol to update my buildroot tree as i'm
> Nicolas> behind a proxy, with address found on your website :
> Nicolas> http://buildroot.uclibc.org/git.html
>
> Nicolas> but since a few days, it seems broken when i try to update.
>
> Nicolas> I do something wrong ?
>
> What exactly happens when you try? It works here:
>
> time git clone -v http://git.buildroot.net/git/buildroot.git
> Cloning into 'buildroot'...
> 5.96s user 2.16s system 5% cpu 2:35.53 total
>
> Notice that it is a lot slower than native git:// access:
>
> time git clone -v git://git.buildroot.net/buildroot
> Cloning into 'buildroot'...
> remote: Counting objects: 111019, done.
> remote: Compressing objects: 100% (41701/41701), done.
> remote: Total 111019 (delta 75790), reused 102807 (delta 68750)
> Receiving objects: 100% (111019/111019), 31.63 MiB | 1.61 MiB/s, done.
> Resolving deltas: 100% (75790/75790), done.
> 3.03s user 0.83s system 9% cpu 41.150 total
>
It's working here as well, although it took 6 minutes.
However, I sniffed the clone operation with wireshark and noticed many
"404 Not Found" errors. I wonder if it is normal with http access.
Luca
next prev parent reply other threads:[~2013-09-05 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 8:14 [Buildroot] git http access broken ? Nicolas Aguirre
2013-09-05 9:25 ` Peter Korsgaard
2013-09-05 9:32 ` Luca Ceresoli [this message]
2013-09-05 10:28 ` Nicolas Aguirre
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=52284FBA.5000400@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--cc=buildroot@busybox.net \
/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.