From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Kevin Lalumiere <klalumiere@coveo.com>
Subject: Re: Blocked IP breaking CIs
Date: Wed, 10 Apr 2024 16:34:21 -0400 [thread overview]
Message-ID: <20240410203421.GC5417@redhat.com> (raw)
In-Reply-To: <DM6PR07MB527643D2D52DD5B4414D4D4CCC062@DM6PR07MB5276.namprd07.prod.outlook.com>
Hi -
> I believe our IPs have been blocked on https://sourceware.org/. Our
> CIs fail [...]
More likely an ongoing (source-IP-dependent!) routing problem is
responsible. Try now, it seems better.
- FChE
prev parent reply other threads:[~2024-04-10 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 20:28 Kevin Lalumiere
2024-04-10 20:34 ` Frank Ch. Eigler [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=20240410203421.GC5417@redhat.com \
--to=fche@redhat.com \
--cc=klalumiere@coveo.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).