From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rich Felker <dalias@libc.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-sh@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: linux-next: error fetching the sh tree
Date: Mon, 09 Jan 2017 20:20:52 +0000 [thread overview]
Message-ID: <20170110072052.4a48d0e8@canb.auug.org.au> (raw)
In-Reply-To: <20170109043305.GA1517@brightrain.aerifal.cx>
Hi Rich,
On Sun, 8 Jan 2017 23:33:05 -0500 Rich Felker <dalias@libc.org> wrote:
>
> It should be back soon (pending dns propagation) if not already. Fire
> took out some of my network infrastructure; for libc.org, just the dns
> was affected.
Ouch! Hope everything else is OK.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-01-09 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 22:25 linux-next: error fetching the sh tree Stephen Rothwell
2017-01-08 22:42 ` John Paul Adrian Glaubitz
2017-01-09 4:33 ` Rich Felker
2017-01-09 20:20 ` 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=20170110072052.4a48d0e8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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;
as well as URLs for NNTP newsgroup(s).