From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.11-rc2
Date: Mon, 13 Mar 2017 13:01:26 -0400 [thread overview]
Message-ID: <20170313170126.GF20608@gmail.com> (raw)
In-Reply-To: <CA+55aFzcXoKcEEiUTdJmxcK0fow2c5aVYoePBdBC2i0mrybwAw@mail.gmail.com>
On Mon, Mar 13, 2017 at 09:15:21AM -0700, Linus Torvalds wrote:
>On Mon, Mar 13, 2017 at 9:05 AM, Josh Boyer <jwboyer@fedoraproject.org> wrote:
>>
>> Yes. A git pull just grabbed it for me. The 'view diff' link on
>> kernel.org still fails with bad object, but I'm guessing that will
>> catch up at some point too.
>
>Hmm. I pushed those before the announcement, so over 18 hours ago by
>now. If there still is something that hasn't mirrored out, that
>implies some problem rather than just a delay.
>
>I don't see anything odd when I go to git.kernel.org, but the
>outward-facing public mirrors are all geolocated, and some of that
>infrastructure is new. So there might be stale DNS information, or
>somethign else going on.
>
>Adding Konstantin to the bcc to notify him. Konstantin: it apparently
>took a long time for the 4.11-rc2 tag to mirror out, and there's still
>some missing object going on.. I'm not sure where Josh is
>geographically, which might matter for the new GeoDNS.
Yes, the EWR mirror was Not Doing The Right Thing, and has been given a
stern talking-to (about an hour ago).
Sorry about that.
-K
prev parent reply other threads:[~2017-03-13 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 22:01 Linux 4.11-rc2 Linus Torvalds
2017-03-13 13:19 ` Josh Boyer
2017-03-13 15:57 ` Linus Torvalds
2017-03-13 16:05 ` Josh Boyer
2017-03-13 16:15 ` Linus Torvalds
2017-03-13 17:01 ` 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=20170313170126.GF20608@gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.