From: Stephen Rothwell <sfr@canb•auug.org.au>
To: schwidefsky@de•ibm.com
Cc: Heiko Carstens <heiko.carstens@de•ibm.com>, linux-next@vger•kernel.org
Subject: Re: linux-next: s390 tree unfetchable
Date: Thu, 24 Jul 2008 09:57:44 +1000 [thread overview]
Message-ID: <20080724095744.2bf583da.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1216844212.19443.6.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
Hi Martin,
On Wed, 23 Jul 2008 22:16:52 +0200 Martin Schwidefsky <schwidefsky@de•ibm.com> wrote:
>
> On Wed, 2008-07-23 at 09:49 +1000, Stephen Rothwell wrote:
> > I have not been able to fetch the s390 tree for a few days now. I get:
> >
> > git390.osdl.marist.edu[0: 148.100.96.69]: errno=Connection refused
>
> Martha fixed it. You should be able to pull from git390 again.
Yep, looks good, thanks.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-07-23 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 23:49 linux-next: s390 tree unfetchable Stephen Rothwell
2008-07-23 7:46 ` Martin Schwidefsky
2008-07-23 20:16 ` Martin Schwidefsky
2008-07-23 23:57 ` Stephen Rothwell [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=20080724095744.2bf583da.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=schwidefsky@de$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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