From: Paul Moore <paul@paul-moore.com>
To: linux-audit@redhat.com
Subject: Re: Upstream kernel development and the linux-audit mailing list
Date: Fri, 3 Feb 2023 11:39:59 -0500 [thread overview]
Message-ID: <CAHC9VhTbnCkOqpsA7f_E0PROu02Q3fi+Z-06T8GuYQg166Wo=w@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhRM16vx4S+2FUcRftvt+DcPe_zASkAyAS4BSzBMFH=pog@mail.gmail.com>
On Tue, Jan 31, 2023 at 2:44 PM Paul Moore <paul@paul-moore.com> wrote:
>
> Hello all,
...
> I'll hold off on list creation for a couple of days in case anyone has
> a well reasoned argument against moving upstream kernel development to
> a new list. However, I want to underscore that any argument to keep
> upstream discussions on a moderated list will need to be strong enough
> to counter potentially excluding other subsystems from the discussion.
Seeing no comments, I just sent a request off to the vger
postmaster(s) to create a new list; I'll send another update when it
is up and running.
--
paul-moore.com
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2023-02-03 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 19:44 Upstream kernel development and the linux-audit mailing list Paul Moore
2023-02-03 16:39 ` Paul Moore [this message]
2023-02-07 15:31 ` Paul Moore
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='CAHC9VhTbnCkOqpsA7f_E0PROu02Q3fi+Z-06T8GuYQg166Wo=w@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=linux-audit@redhat.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;
as well as URLs for NNTP newsgroup(s).