From: Lachlan McIlroy <lachlan@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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, 07 Nov 2008 15:51:51 +1100 [thread overview]
Message-ID: <4913C967.30309@sgi.com> (raw)
In-Reply-To: <20081107154602.8621ea3d.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> 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.
>
I actually got a bounce message when I sent that reply. Gotta love the irony.
next prev parent reply other threads:[~2008-11-07 4:53 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
2008-11-07 4:51 ` Lachlan McIlroy [this message]
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=4913C967.30309@sgi.com \
--to=lachlan@sgi.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxf-fsdevel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.