workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: linux-doc@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: workflows@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Randy Dunlap <rdunlap@infradead.org>,
	regressions@lists.linux.dev,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH v3 0/2] docs: add a text about regressions to the Linux kernel's documentation
Date: Tue, 25 Jan 2022 12:44:12 +0100	[thread overview]
Message-ID: <cover.1643110442.git.linux@leemhuis.info> (raw)

'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.

v3 (this mail):
- drop RFC tag
- heavily reshuffled and slightly adjusted the text in the sections "The
  important bits for people fixing regressions" and "How to add a regression to
  regzbot's tracking somebody else reported?" to make them easier to grasp
- a few small fixes and improvements
- add ACK for the series from Greg (now for real)

v2/RFC (https://lore.kernel.org/linux-doc/cover.1641565030.git.linux@leemhuis.info/):
- 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

v1/RFC (https://lore.kernel.org/linux-doc/cover.1641203216.git.linux@leemhuis.info/):
- initial version

---

Hi! Merge window is over, so I'd like to move on with this. Dropped the RFC tag;
I had a small hope Linus would take a look at this (especially the second patch)
before I remove it; well, didn't work out, but Greg ACKed it, which is good
enough reason to move on with this. :-D

Ciao, Thorsten

Thorsten Leemhuis (2):
  docs: add a document about regression handling
  docs: regressions.rst: rules of thumb for handling regressions

 Documentation/admin-guide/index.rst       |   1 +
 Documentation/admin-guide/regressions.rst | 992 ++++++++++++++++++++++
 MAINTAINERS                               |   1 +
 3 files changed, 994 insertions(+)
 create mode 100644 Documentation/admin-guide/regressions.rst


base-commit: e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
-- 
2.31.1


             reply	other threads:[~2022-01-25 11:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 11:44 Thorsten Leemhuis [this message]
2022-01-25 11:44 ` [PATCH v3 1/2] docs: add a document about regression handling Thorsten Leemhuis
2022-01-25 23:59   ` Jonathan Corbet
2022-01-26 14:10     ` Thorsten Leemhuis
2022-01-26 17:16       ` Randy Dunlap
2022-01-31 14:22       ` Thorsten Leemhuis
2022-01-26 14:28   ` Geert Uytterhoeven
2022-02-02 11:46     ` Thorsten Leemhuis
2022-01-25 11:44 ` [PATCH v3 2/2] docs: regressions.rst: rules of thumb for handling 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=cover.1643110442.git.linux@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox