From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: fatal: The remote end hung up unexpectedly
Date: Wed, 15 Sep 2010 14:00:12 +0200 [thread overview]
Message-ID: <4C90B54C.1080907@dresearch.de> (raw)
In-Reply-To: <AANLkTik1N_3sFrOqsWoBrcCSdYmBLoCOPdv-0dRwWzzB@mail.gmail.com>
Am 15.09.2010 13:52, schrieb Frans Meulenbroeks:
> 2010/9/15 Steffen Sledz <sledz@dresearch.de>:
>> Can't push my changes today. :(
>>
>>> git push -v upstream
>> Pushing to git://git.openembedded.net/openembedded
>> fatal: The remote end hung up unexpectedly
>>
>> Steffen
>>
>
> Hm.
> I see that every once in a while too when doing a pull. Pulling a
> second time then often works for me, but I guess you tried pushing a
> 2nd time.
A lot more.
And from different machines.
> And there are no new changes for 13 hrs.
> Guess we'll have to wait for the west coast to wake up
;-)
next prev parent reply other threads:[~2010-09-15 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 11:02 fatal: The remote end hung up unexpectedly Steffen Sledz
2010-09-15 11:52 ` Frans Meulenbroeks
2010-09-15 12:00 ` Steffen Sledz [this message]
2010-09-16 10:20 ` Steffen Sledz
2010-09-16 10:40 ` Paul Menzel
2010-09-16 12:12 ` Frans Meulenbroeks
2010-09-16 16:20 ` Paul Menzel
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=4C90B54C.1080907@dresearch.de \
--to=sledz@dresearch.de \
--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 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.