From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Robert Nelson <robertcnelson@gmail.com>,
helpdesk@kernel.org, Jiri Slaby <jslaby@suse.cz>,
Greg KH <gregkh@linuxfoundation.org>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.10.2
Date: Mon, 13 Mar 2017 12:03:09 -0400 [thread overview]
Message-ID: <20170313160309.GD20608@gmail.com> (raw)
In-Reply-To: <CAKb7UvjW+KVg2oexNSRTZDk82soAoVyTkQ+AbTT+nqh_8iWoWw@mail.gmail.com>
On Mon, Mar 13, 2017 at 11:44:18AM -0400, Ilia Mirkin wrote:
>> rcnee@debian:~/linux$ host git.kernel.org
>> git.kernel.org is an alias for pub.kernel.org.
>> pub.kernel.org is an alias for pub.ewr.kernel.org.
>> pub.ewr.kernel.org has address 147.75.196.57
>> pub.ewr.kernel.org has IPv6 address 2604:1380:1:3600::3
>
>$ git fetch origin
>remote: Counting objects: 2543, done.
>remote: Compressing objects: 100% (725/725), done.
>remote: Total 2543 (delta 2112), reused 2207 (delta 1816)
>Receiving objects: 100% (2543/2543), 503.18 KiB | 0 bytes/s, done.
>Resolving deltas: 100% (2112/2112), completed with 675 local objects.
>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
> c1ae3cf..56b24d1 master -> origin/master
>$ git show v4.11-rc2
>fatal: ambiguous argument 'v4.11-rc2': unknown revision or path not in
>the working tree.
>Use '--' to separate paths from revisions, like this:
>'git <command> [<revision>...] -- [<file>...]'
>$ git tag -l *4.11-rc[12]
>v4.11-rc1
>$ host git.kernel.org
>git.kernel.org is an alias for pub.kernel.org.
>pub.kernel.org is an alias for pub.ewr.kernel.org.
>pub.ewr.kernel.org has address 147.75.196.57
>pub.ewr.kernel.org has IPv6 address 2604:1380:1:3600::3
>
>Coincidence? (I'm in NYC in case it matters. I'm using IPv4 from here,
>but was most likely on IPv6 at home yesterday when I first had the
>issue.)
I've identified and fixed the mirroring issue with the EWR frontend.
All repositories should now be up-to-date. Apologies about the problem!
-Konstantin
next prev parent reply other threads:[~2017-03-13 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-38150@linuxfoundation>
2017-03-12 13:05 ` Linux 4.10.2 Greg KH
2017-03-12 18:51 ` Robert Nelson
2017-03-12 19:05 ` Greg KH
2017-03-12 20:11 ` Ilia Mirkin
2017-03-12 20:47 ` Alexander Kapshuk
2017-03-13 12:36 ` Jiri Slaby
2017-03-13 13:55 ` Ilia Mirkin
2017-03-13 15:23 ` Robert Nelson
2017-03-13 15:32 ` Robert Nelson
2017-03-13 15:35 ` Konstantin Ryabitsev
2017-03-13 15:36 ` [Kernel.org Helpdesk #38150] [linuxfoundation.org #38150] " Konstantin Ryabitsev via RT
2017-03-13 15:38 ` Robert Nelson
2017-03-13 15:39 ` [Kernel.org Helpdesk #38150] [linuxfoundation.org #38150] " Robert Nelson via RT
2017-03-13 15:44 ` Ilia Mirkin
2017-03-13 15:44 ` [Kernel.org Helpdesk #38150] [linuxfoundation.org #38150] " imirkin@alum.mit.edu via RT
2017-03-13 16:03 ` Konstantin Ryabitsev [this message]
2017-03-13 16:03 ` Konstantin Ryabitsev via RT
2017-03-13 16:04 ` Robert Nelson
2017-03-13 16:05 ` [Kernel.org Helpdesk #38150] [linuxfoundation.org #38150] " Robert Nelson via RT
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=20170313160309.GD20608@gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=helpdesk@kernel.org \
--cc=imirkin@alum.mit.edu \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=robertcnelson@gmail.com \
/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