public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Guillaume Gardet <guillaume.gardet@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Git clone using http or rsync broken
Date: Mon, 23 Feb 2015 09:39:01 +0100	[thread overview]
Message-ID: <54EAE725.4000600@free.fr> (raw)
In-Reply-To: <CALxOYEbX09e7JD1TeZD=boVBMfmJN3SkOLG9CV5SgY-BWjsFCg@mail.gmail.com>


Le 21/02/2015 13:19, Nable a ?crit :
> Hi!
>
> Rsync isn't mentioned here: http://git.denx.de/u-boot.git/ , this fact
> makes me think that rsync support isn't present.

Ok.

>
> 2.
>> "git clone http://git.denx.de/u-boot.git" just hangs with:
>>   Cloning into 'u-boot'...
> U-Boot repo is very large, so it takes a lot of time and traffic to
> clone it. Are you sure that git clone hangs? It you enable enough
> verbosity, you'll see that git is doing something:
> $ git clone -vvvvvv http://git.denx.de/u-boot.git
> Cloning into 'u-boot'...
> Getting alternates list for http://git.denx.de/u-boot.git
> Getting pack list for http://git.denx.de/u-boot.git
> Getting index for pack 09e0accc51ea3a5c8d84fdf7fe7193bf7c7b51ff
> ...
> You can also use some network activity monitor to see that git is
> silently downloading a lot of information.

Testing again right now and it seems to work fine.

>
> Btw, git:// protocol works fine, do you have any reasons to avoid using it?
>

Here, GIT protocol works fine but on some of my client networks, GIT is unreachable (probably due to proxy or firewall) and thus HTTP must be used instead.


Guillaume

      reply	other threads:[~2015-02-23  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 12:54 [U-Boot] Git clone using http or rsync broken Guillaume Gardet
2015-02-21 12:19 ` Nable
2015-02-23  8:39   ` Guillaume Gardet [this message]

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=54EAE725.4000600@free.fr \
    --to=guillaume.gardet@free.fr \
    --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