workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiri Kosina <jkosina@suse.cz>,
	security@kernel.org, workflows@vger.kernel.org,
	Kees Cook <keescook@chromium.org>,
	Solar Designer <solar@openwall.com>,
	Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH] Documentation: security-bugs.rst: linux-distros relaxed their rules
Date: Tue, 24 Oct 2023 18:20:03 +0200	[thread overview]
Message-ID: <ZTfus7qKp2R5azJG@1wt.eu> (raw)
In-Reply-To: <2023102402-unheated-basis-55e5@gregkh>

On Tue, Oct 24, 2023 at 11:24:27AM +0200, Greg Kroah-Hartman wrote:
> On Sun, Oct 22, 2023 at 08:31:45PM -0600, Jonathan Corbet wrote:
> > Willy Tarreau <w@1wt.eu> writes:
> > 
> > > The linux-distros list relaxed their rules to try to adapt better to
> > > how the Linux kernel works. Let's update the Coordination part to
> > > explain why and when to contact them or not to and how to avoid trouble
> > > in the future.
> > >
> > > Link: https://www.openwall.com/lists/oss-security/2023/09/08/4
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Cc: Kees Cook <keescook@chromium.org>
> > > Cc: Solar Designer <solar@openwall.com>
> > > Cc: Vegard Nossum <vegard.nossum@oracle.com>
> > > Acked-by: Jiri Kosina <jkosina@suse.cz>
> > > Signed-off-by: Willy Tarreau <w@1wt.eu>
> > > ---
> > >
> > > This is the final version for merging. Changes since RFC:
> > >   - s/BEFORE/UNTIL from Vegard
> > >   - improved wording from Alexander
> > >   - acked-by from Jiri
> > 
> > Greg, you've taken changes to this file in the past; do you want to grab
> > this one or should I pick it up?
> 
> I was hoping there would be other reviewers of it, but I guess not.

I'm pretty sure non-technical stuff like this actually bores everyone,
starting from us; when I proposed you to work on it, I was already
convinced that nobody would have stolen me that task!

> I'll take it through my tree now, thanks!

Thank you!
Willy

      reply	other threads:[~2023-10-24 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15 13:09 Willy Tarreau
2023-10-23  2:31 ` Jonathan Corbet
2023-10-24  9:24   ` Greg Kroah-Hartman
2023-10-24 16:20     ` Willy Tarreau [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=ZTfus7qKp2R5azJG@1wt.eu \
    --to=w@1wt.eu \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=solar@openwall.com \
    --cc=vegard.nossum@oracle.com \
    --cc=workflows@vger.kernel.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