From: Stephen Rothwell <sfr@canb•auug.org.au>
To: lachlan@sgi•com
Cc: David Chinner <david@fromorbit•com>,
linux-next@vger•kernel.org, linuxf-fsdevel@vger•kernel.org,
LKML <linux-kernel@vger•kernel.org>,
Christoph Hellwig <hch@infradead•org>
Subject: Re: linux-next: unable to fetch the xfs tree
Date: Fri, 7 Nov 2008 15:46:02 +1100 [thread overview]
Message-ID: <20081107154602.8621ea3d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4913BEC6.6080901@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Hi Lachlan,
On Fri, 07 Nov 2008 15:06:30 +1100 Lachlan McIlroy <lachlan@sgi•com> wrote:
>
> Stephen Rothwell wrote:
> > Hi all,
> >
> > On Fri, 7 Nov 2008 11:11:25 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >> I am getting:
> >>
> >> oss.sgi.com[0: 192.48.170.157]: errno=Connection refused
> >>
> >> so I will use what I fetched yesterday.
> >
> > And now I have received:
> >
> > <xfs-masters@oss•sgi.com>: host cuda-allmx.sgi.com[192.48.176.16] said: 550
> > cuda_nsu 5.1.1 <xfs-masters@oss•sgi.com>... User unknown (in reply to RCPT
> > TO command)
> >
> > So, is this a permanent state of affairs, or just a temporary glitch?
>
> Should be temporary. We have known DNS and email issues that we are working
> on. We're also moving oss.sgi.com but I have no idea what the schedule is.
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 --]
next prev parent reply other threads:[~2008-11-07 4:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 0:11 linux-next: unable to fetch the xfs tree Stephen Rothwell
2008-11-07 3:53 ` Stephen Rothwell
2008-11-07 4:06 ` Lachlan McIlroy
2008-11-07 4:46 ` Stephen Rothwell [this message]
2008-11-07 4:51 ` Lachlan McIlroy
2008-11-07 5:13 ` Stephen Rothwell
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=20081107154602.8621ea3d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=david@fromorbit$(echo .)com \
--cc=hch@infradead$(echo .)org \
--cc=lachlan@sgi$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxf-fsdevel@vger$(echo .)kernel.org \
/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