From: Johan Hovold <johan@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Jonathan Corbet <corbet@lwn.net>,
skhan@linuxfoundation.org, Randy Dunlap <rdunlap@infradead.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
gregkh@linuxfoundation.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH 05/14] docs: security-bugs: explain how to send a fix that can be applied
Date: Fri, 13 Nov 2026 13:34:52 +0100 [thread overview]
Message-ID: <avcD7Dvj-HXQmziQ@hovoldconsulting.com> (raw)
In-Reply-To: <20261109080240.29444-6-w@1wt.eu>
On Mon, Nov 09, 2026 at 09:02:31AM +0100, Willy Tarreau wrote:
> +Sending a fix
> +~~~~~~~~~~~~~
> +
> +Most fixes sent along with reports cannot be applied as-is, because they were
I'd drop the comma after "as-is".
> +damaged by the mailer or lacking a commit message, forcing maintainers to ask
> +for a resend. A fix must be applicable using ``git am``, which is most easily
> +achieved by letting git produce and send the messages (see
> +Documentation/process/submitting-patches.rst).
Johan
next prev parent reply other threads:[~2026-11-13 12:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 8:02 [PATCH 00/14] security-bugs doc updates Willy Tarreau
2026-11-09 8:02 ` [PATCH 01/14] docs: security-bugs: reorganize the document without changing its contents Willy Tarreau
2026-11-09 8:02 ` [PATCH 02/14] docs: security-bugs: clarify when to Cc the security team Willy Tarreau
2026-11-13 12:17 ` Johan Hovold
2026-11-09 8:02 ` [PATCH 03/14] docs: security-bugs: never publish reproducers of bugs with a security impact Willy Tarreau
2026-11-09 8:02 ` [PATCH 04/14] docs: threat-model: clarify the case of automatically mounted file systems Willy Tarreau
2026-11-09 8:02 ` [PATCH 05/14] docs: security-bugs: explain how to send a fix that can be applied Willy Tarreau
2026-11-13 12:34 ` Johan Hovold [this message]
2026-11-09 8:02 ` [PATCH 06/14] docs: security-bugs: do not send archives or binary attachments Willy Tarreau
2026-11-09 8:02 ` [PATCH 07/14] docs: security-bugs: first-time reporters must send a single report first Willy Tarreau
2026-11-09 8:02 ` [PATCH 08/14] docs: security-bugs: explain what to do when a report gets no response Willy Tarreau
2026-11-09 8:02 ` [PATCH 09/14] docs: security-bugs: reports left unanswered for 7 days will be dropped Willy Tarreau
2026-11-09 8:02 ` [PATCH 10/14] docs: security-bugs: add a section for maintainers receiving reports Willy Tarreau
2026-11-09 8:02 ` [PATCH 11/14] docs: security-bugs: explain why directly sent reports add extra work Willy Tarreau
2026-11-09 8:02 ` [PATCH 12/14] docs: security-bugs: explain why AI-found bugs are handled publicly Willy Tarreau
2026-11-09 8:02 ` [PATCH 13/14] docs: submitting-patches: defer to security-bugs.rst for security fixes Willy Tarreau
2026-11-09 8:02 ` [PATCH 14/14] docs: netdev: align the security fixes section with security-bugs.rst Willy Tarreau
2026-11-09 16:00 ` Jakub Kicinski
2026-11-09 17:32 ` Willy Tarreau
2026-11-13 12:07 ` [PATCH 00/14] security-bugs doc updates Johan Hovold
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=avcD7Dvj-HXQmziQ@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=w@1wt.eu \
--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