Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: git issues
Date: Thu, 02 Sep 2010 07:23:25 -0600	[thread overview]
Message-ID: <4C7FA54D.5070908@mlbassoc.com> (raw)
In-Reply-To: <AANLkTinhxdSG3M3ddEa6Bgtbkp4Pg8H5MSxkUAgWGZUk@mail.gmail.com>

On 09/02/2010 06:59 AM, Frans Meulenbroeks wrote:
> For some reason recently every once in a while on a git pull or git
> clone I get an error like this:
>
> git clone git://git.openembedded.net/openembedded openembedded
> Initialized empty Git repository in
> /home/frans/workspace/Linux/openembedded-test/openembedded/.git/
> fatal: The remote end hung up unexpectedly
> make: *** [all] Error 128
>
> Repeating the command often makes it work.
>
> Also I notice that the transfer rate is about 100-120 KB/s
> I seem to recall Leon also reported something like this with irc.
>
> Is this something others see as well?
> Especially the hangup does not really help to set up an automated test system.

I've seen this on a number of sites, not just OE.  As you say, trying
again makes it happy.

I think it's a generic GIT problem (at least that's my experience)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



  parent reply	other threads:[~2010-09-02 13:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 12:59 git issues Frans Meulenbroeks
2010-09-02 13:21 ` git issues: `fatal: The remote end hung up unexpectedly` and small bandwidth Paul Menzel
2010-09-02 13:23 ` Gary Thomas [this message]
2010-09-02 14:14   ` git issues Maupin, Chase
2010-09-02 14:50     ` Jesse Gilles
2010-09-02 23:49 ` Cliff Brake
2010-09-03  8:36 ` Leon Woestenberg

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=4C7FA54D.5070908@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-devel@lists.openembedded.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