From: Jonathan Corbet <corbet@lwn.net>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>, Willy Tarreau <w@1wt.eu>,
Ben Hutchings <ben@decadent.org.uk>,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH v2.5] docs: backporting: address feedback
Date: Thu, 26 Oct 2023 11:50:15 -0600 [thread overview]
Message-ID: <877cn96zoo.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231023135722.949510-1-vegard.nossum@oracle.com>
Vegard Nossum <vegard.nossum@oracle.com> writes:
> This addresses a few comments/issues in my v2 submission:
>
> - repeated word: 'run' from kernel test robot
> - emacs/ediff mode from Jon Corbet
> - various comments from Willy Tarreau
> - more backporting advice from Ben Hutchings
> - a couple more cherry-pick tips from Harshit Mogalapalli
> - add a bit about stable submissions
>
> Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
> ---
> Documentation/process/backporting.rst | 152 ++++++++++++++++++++------
> 1 file changed, 121 insertions(+), 31 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2023-10-26 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 9:23 [PATCH v2] docs: add backporting and conflict resolution document Vegard Nossum
2023-10-03 15:19 ` Jonathan Corbet
2023-10-10 19:57 ` Jonathan Corbet
2023-10-13 15:24 ` Vegard Nossum
2023-10-14 9:43 ` Willy Tarreau
2023-10-14 11:48 ` Vegard Nossum
2023-10-14 15:07 ` Willy Tarreau
2023-10-17 16:42 ` Ben Hutchings
2023-10-23 13:57 ` [PATCH v2.5] docs: backporting: address feedback Vegard Nossum
2023-10-26 17:50 ` Jonathan Corbet [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=877cn96zoo.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Jason@zx2c4.com \
--cc=bagasdotme@gmail.com \
--cc=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=vegard.nossum@oracle.com \
--cc=w@1wt.eu \
/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