From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux_dti@icloud.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
webmaster@kernel.org
Subject: Re: [sysadmin] Re: linux-next: Tree for Oct 29
Date: Mon, 29 Oct 2018 08:43:20 -0400 [thread overview]
Message-ID: <20181029124320.GA9047@pure.paranoia.local> (raw)
In-Reply-To: <CAMuHMdXM+Zcx_CnwPZyvz7JUD+r1eQ-MFv43kKAg1_cNMhLzvQ@mail.gmail.com>
On Mon, Oct 29, 2018 at 01:16:59PM +0100, Geert Uytterhoeven wrote:
> I can confirm syd.git.kernel.org and ord.git.kernel.org have it, but
> fra.git.kernel.org (my default) hasn't.
The Frankfurt frontend lost the VPN connection to our main infra. I'm
checking why the alerts for that didn't fire properly, but for now it's
at least back to properly replicating.
-K
prev parent reply other threads:[~2018-10-29 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 6:02 linux-next: Tree for Oct 29 Stephen Rothwell
2018-10-29 6:33 ` Damian Tometzki
2018-10-29 9:41 ` Stephen Rothwell
2018-10-29 11:42 ` damian
2018-10-29 12:08 ` Stephen Rothwell
2018-10-29 12:16 ` Geert Uytterhoeven
2018-10-29 12:43 ` Konstantin Ryabitsev [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=20181029124320.GA9047@pure.paranoia.local \
--to=konstantin@linuxfoundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_dti@icloud.com \
--cc=sfr@canb.auug.org.au \
--cc=webmaster@kernel.org \
/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