All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	workflows@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Randy Dunlap <rdunlap@infradead.org>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [RFC PATCH v2 0/2] docs: add a text about regressions to the Linux kernel's documentation
Date: Fri, 7 Jan 2022 17:41:15 +0100	[thread overview]
Message-ID: <5d0c6929-721e-0887-20f0-b9922840504c@leemhuis.info> (raw)
In-Reply-To: <YdhqNHI/f2B/SlcE@kroah.com>

On 07.01.22 17:28, Greg Kroah-Hartman wrote:
> On Fri, Jan 07, 2022 at 03:21:00PM +0100, Thorsten Leemhuis wrote:
>> 'We don't cause regressions' might be the first rule of Linux kernel
>> development, but it and other aspects of regressions nevertheless are hardly
>> described in the Linux kernel's documentation. The following two patches change
>> this by creating a document dedicated to the topic.
>>
>> The second patch could easily be folded into the first one, but was kept
>> separate, as it might be a bit controversial. This also allows the patch
>> description to explain some backgrounds for this part of the document.
>> Additionally, ACKs and Reviewed-by tags can be collected separately this way.
>>
>> v2/RFC:
>> - a lot of small fixes, most are for spelling mistakes and grammar
>>   errors/problems pointed out in the review feedback I got so far
>> - add ACK for the series from Greg
> 
> My ack seems not to be here :(

Huh, how did that happen? Sorry, thx for pointing it out, will be in v3.

> Also, this is a "real" series, no need for a RFC anymore, right?

I was taken a bit back-and-forth and then settled on calling this one
still RFC, as I was unsure if people Jon might want to wait on feedback
from Linus before they take

  reply	other threads:[~2022-01-07 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 14:21 [RFC PATCH v2 0/2] docs: add a text about regressions to the Linux kernel's documentation Thorsten Leemhuis
2022-01-07 14:21 ` [RFC PATCH v2 1/2] docs: add a document about regression handling Thorsten Leemhuis
2022-01-07 15:37   ` Matthias Brugger
2022-01-07 16:51     ` Thorsten Leemhuis
2022-01-07 17:44       ` Matthias Brugger
2022-01-10 11:40         ` Thorsten Leemhuis
2022-01-10 12:13           ` Matthias Brugger (SUSE)
2022-01-07 14:21 ` [RFC PATCH v2 2/2] docs: regressions.rst: rules of thumb for handling regressions Thorsten Leemhuis
2022-01-07 16:28 ` [RFC PATCH v2 0/2] docs: add a text about regressions to the Linux kernel's documentation Greg Kroah-Hartman
2022-01-07 16:41   ` Thorsten Leemhuis [this message]
2022-01-07 16:42   ` Thorsten Leemhuis

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=5d0c6929-721e-0887-20f0-b9922840504c@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.