From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Ian Kelling <iank@fsf.org>,
Overseers mailing list <overseers@sourceware.org>,
gdb@sourceware.org, Mark Wielaard <mark@klomp.org>,
libc-alpha@sourceware.org, binutils@sourceware.org,
gcc@gcc.gnu.org
Subject: Re: Toolchain Infrastructure project statement of support
Date: Sun, 23 Oct 2022 14:56:56 -0400 [thread overview]
Message-ID: <20221023185656.f7jvtauavqy7nz7y@meerkat.local> (raw)
In-Reply-To: <58918ca9-70dd-8724-82e0-684350e2207e@gotplt.org>
On Sun, Oct 23, 2022 at 12:17:36PM -0400, Siddhesh Poyarekar wrote:
> > Let's consider some "established security and administration practices"
> >
> > curl -v http://vger.kernel.org | head
These are all very fair observations, with one important caveat --
vger.kernel.org is the last remaining piece of kernel.org infrastructure that
is not managed by our team. It's been historically maintained by volunteers
that are not associated with the Linux Foundation (vger used to be hosted at
Red Hat, iirc).
> +Konstantin from LF IT since he's better equipped to speak to this, although
> ISTM that they started migrating off vger last year[1].
Correct, everything is ready for the migration on our end, but we cannot
unilaterally initiate the process. The mail server maintained by the Linux
Foundation is at subspace.kernel.org. I invite you to poke at it to see if it
fares any better compared to vger.
Best wishes,
Konstantin
next prev parent reply other threads:[~2022-10-23 18:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2513b668-9ebd-9e78-7263-dc24f4a9558a@redhat.com>
2022-10-13 18:25 ` Christopher Faylor
2022-10-14 12:33 ` Siddhesh Poyarekar
2022-10-17 15:10 ` Mark Wielaard
2022-10-17 16:11 ` Siddhesh Poyarekar
2022-10-18 9:50 ` Mark Wielaard
2022-10-18 15:17 ` Siddhesh Poyarekar
2022-10-18 16:42 ` Christopher Faylor
2022-10-18 18:13 ` Siddhesh Poyarekar
2022-10-18 18:14 ` Siddhesh Poyarekar
2022-10-18 18:47 ` Paul Smith
2022-10-21 0:33 ` Alexandre Oliva
2022-10-23 8:59 ` Ian Kelling
2022-10-23 13:27 ` Siddhesh Poyarekar
2022-10-23 15:16 ` Frank Ch. Eigler
2022-10-23 16:07 ` Siddhesh Poyarekar
2022-10-23 16:32 ` Siddhesh Poyarekar
2022-10-23 17:01 ` Jeff Law
2022-10-23 22:35 ` Christopher Faylor
2022-10-23 17:09 ` Frank Ch. Eigler
2022-10-23 17:38 ` Jeff Law
2022-10-24 1:51 ` Siddhesh Poyarekar
2022-10-23 20:57 ` Christopher Faylor
2022-10-23 21:17 ` Siddhesh Poyarekar
2022-10-23 21:59 ` Christopher Faylor
2022-10-24 1:29 ` Siddhesh Poyarekar
2022-10-23 11:33 ` Ian Kelling
2022-10-23 16:17 ` Siddhesh Poyarekar
2022-10-23 18:56 ` Konstantin Ryabitsev [this message]
2022-10-23 21:19 ` Alexandre Oliva
2022-10-23 22:07 ` Christopher Faylor
2022-10-12 17:40 Carlos O'Donell
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=20221023185656.f7jvtauavqy7nz7y@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=iank@fsf.org \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=siddhesh@gotplt.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).