From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>,
linux-doc@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: workflows@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
regressions@lists.linux.dev,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH v5 0/3] docs: add two texts covering regressions
Date: Thu, 24 Feb 2022 12:58:03 -0700 [thread overview]
Message-ID: <871qzskpf8.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1644994117.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> "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 patches change
> this by creating two documents 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.
Hearing no objections, I have applied this set, thanks.
jon
next prev parent reply other threads:[~2022-02-24 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 6:51 [PATCH v5 0/3] docs: add two texts covering regressions Thorsten Leemhuis
2022-02-16 6:51 ` [PATCH v5 1/3] docs: add two documents about regression handling Thorsten Leemhuis
2022-02-16 6:51 ` [PATCH v5 2/3] docs: *-regressions.rst: explain how quickly issues should be handled Thorsten Leemhuis
2022-02-16 6:51 ` [PATCH v5 3/3] docs: reporting-issues.rst: link new document about regressions Thorsten Leemhuis
2022-02-24 19:58 ` Jonathan Corbet [this message]
2022-02-25 11:56 ` [PATCH v5 0/3] docs: add two texts covering regressions 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=871qzskpf8.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
--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.