From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Cc: Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: git.openembedded.org down?
Date: Thu, 17 Feb 2011 12:22:19 +0100 [thread overview]
Message-ID: <4D5D04EB.2020300@dresearch.de> (raw)
In-Reply-To: <1297937814.3959.0.camel@mattotaupa>
Am 17.02.2011 11:16, schrieb Paul Menzel:
> Am Donnerstag, den 17.02.2011, 08:30 +0100 schrieb Steffen Sledz:
>> sledz@fsc-480-012-88:~/work/openembedded> git fetch upstream
>> ssh: connect to host git.openembedded.org port 22: Connection timed out
>> fatal: The remote end hung up unexpectedly
>
> <git://git.openembedded.org/openembedded.git> works fine for me.
It seems to be back again.
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
prev parent reply other threads:[~2011-02-17 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 7:30 git.openembedded.org down? Steffen Sledz
2011-02-17 10:16 ` Paul Menzel
2011-02-17 11:22 ` Steffen Sledz [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=4D5D04EB.2020300@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paulepanter@users.sourceforge.net \
/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.