From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Salil Mehta <salil.mehta@huawei.com>
Cc: Salil Mehta <salil.mehta@opnsrc.net>,
"Michael S. Tsirkin" <mtsirkin@redhat.com>,
"helpdesk@kernel.org" <helpdesk@kernel.org>,
"meta@public-inbox.org" <meta@public-inbox.org>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Question] review links are disappearing from the qemu-devel mailing-list
Date: Mon, 13 Nov 2023 15:44:05 -0500 [thread overview]
Message-ID: <20231113-lavender-agama-of-honeydew-681a58@nitro> (raw)
In-Reply-To: <b1ac3d105e5a4069b1d01b0afaf8de88@huawei.com>
On Mon, Nov 13, 2023 at 07:39:21PM +0000, Salil Mehta wrote:
> > When you go to "git.kernel.org" on your company network, what city do you
> > have in the header ("dallas", "amsterdam", etc).
>
> I am seeing below in the header:
>
> Git repositories hosted at kernel.org (amsterdam)
This is really strange, I am able to retrieve that URL without any problems on
all lore.kernel.org nodes. E.g.:
$ curl -sL -H 'Host: lore.kernel.org' -I https://dfw.source.kernel.org/qemu-devel/20231027145652.44cc845c@imammedo.users.ipa.redhat.com/ | head -n1
HTTP/1.1 200 OK
$ curl -sL -H 'Host: lore.kernel.org' -I https://ams.source.kernel.org/qemu-devel/20231027145652.44cc845c@imammedo.users.ipa.redhat.com/ | head -n1
HTTP/1.1 200 OK
$ curl -sL -H 'Host: lore.kernel.org' -I https://sin.source.kernel.org/qemu-devel/20231027145652.44cc845c@imammedo.users.ipa.redhat.com/ | head -n1
HTTP/1.1 200 OK
I am very curious why it's not working for you. When you run "ping
lore.kernel.org", which IP address do you get?
-K
next prev parent reply other threads:[~2023-11-13 20:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49f4357be7c4470fa1f0398e346c0173@huawei.com>
2023-11-06 16:49 ` [Question] review links are disappearing from the qemu-devel mailing-list Michael S. Tsirkin
2023-11-06 16:51 ` Michael S. Tsirkin
2023-11-06 17:36 ` Eric Wong
2023-11-07 9:54 ` Salil Mehta
2023-11-07 9:57 ` Michael S. Tsirkin
2023-11-07 9:50 ` Salil Mehta
2023-11-07 13:42 ` Igor Mammedov
2023-11-07 13:51 ` Michael S. Tsirkin
2023-11-08 9:30 ` Igor Mammedov
2023-11-08 10:04 ` Salil Mehta
2023-11-06 18:18 ` Konstantin Ryabitsev
2023-11-07 9:57 ` Salil Mehta
2023-11-07 13:56 ` Konstantin Ryabitsev
2023-11-07 14:14 ` Michael S. Tsirkin
2023-11-13 19:27 ` Salil Mehta
2023-11-13 19:32 ` Konstantin Ryabitsev
2023-11-13 19:39 ` Salil Mehta
2023-11-13 20:44 ` Konstantin Ryabitsev [this message]
2023-11-13 22:26 ` Salil Mehta
2023-11-14 11:03 ` Salil Mehta
2023-11-14 15:10 ` Konstantin Ryabitsev
2023-11-14 16:11 ` Salil Mehta
2023-11-14 16:46 ` Konstantin Ryabitsev
2023-11-14 15:32 ` Eric Wong
2023-11-14 16:21 ` Salil Mehta
2023-11-14 16:36 ` Eric Wong
2023-11-14 16:59 ` Konstantin Ryabitsev
2023-11-14 17:21 ` Eric Wong
2023-11-14 17:25 ` Salil Mehta
2023-11-15 11:14 ` Salil Mehta
2023-11-13 19:33 ` Salil Mehta
2023-11-07 9:46 ` Salil Mehta
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231113-lavender-agama-of-honeydew-681a58@nitro \
--to=konstantin@linuxfoundation.org \
--cc=helpdesk@kernel.org \
--cc=imammedo@redhat.com \
--cc=meta@public-inbox.org \
--cc=mtsirkin@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=salil.mehta@opnsrc.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).