Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Christophe Aeschlimann <c.aeschlimann@acn-group.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE git repo down?
Date: Mon, 07 Jun 2010 11:28:57 +0200	[thread overview]
Message-ID: <4C0CBBD9.5000909@acn-group.ch> (raw)
In-Reply-To: <alpine.DEB.2.00.1006070501210.14095@lynx>

Le 07.06.2010 11:06, Robert P. J. Day a écrit :
>
>    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.
>
> rday
>

You broke it down by submitting too many documentation updates ! :)

It's not responsive here neither.

Regards,

-- 
Christophe Aeschlimann

Embedded Software Engineer

Advanced Communications Networks S.A.

Rue du Puits-Godet 8a
2000 Neuchâtel, Switzerland

Tél. +41 32 724 74 31

c.aeschlimann@acn-group.ch



  reply	other threads:[~2010-06-07  9:33 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 [this message]
2010-06-07  9:36   ` Robert P. J. Day
2010-06-07 10:21 ` Koen Kooi

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=4C0CBBD9.5000909@acn-group.ch \
    --to=c.aeschlimann@acn-group.ch \
    --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