From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE git repo down?
Date: Mon, 07 Jun 2010 12:21:57 +0200 [thread overview]
Message-ID: <huih85$dh2$1@dough.gmane.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1006070501210.14095@lynx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07-06-10 11:06, Robert P. J. Day wrote:
>
> for the last couple hours, i've had persistent errors trying to
> update my git working copy of OE:
>
> fatal: read error: Connection reset by peer
>
> is this a known issue? things were working fine yesterday.
I can't reach it from here as well, would be nice if the server admins
dropped us a note about the situation...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMDMhFMkyGM64RGpERAtmBAJ4k4ZN3KJwnPLt0AH+hYfHrWG39GgCfQV+P
smHQ4xUeVL09dTty9eP/Sag=
=zVjQ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-06-07 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 9:06 OE git repo down? Robert P. J. Day
2010-06-07 9:28 ` Christophe Aeschlimann
2010-06-07 9:36 ` Robert P. J. Day
2010-06-07 10:21 ` Koen Kooi [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='huih85$dh2$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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