tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: *-regressions.rst: unify quoting, add missing word

Quoting of the '"no regressions" rule' expression differs between
occurrences, sometimes being presented as '"no regressions rule"'. Unify
the quoting using the first form which seems semantically correct or is
at least used dominantly, albeit marginally.

One of the occurrences is obviously missing the 'rule' part -- add it.

Signed-off-by: Karel Balej <balejk@matfyz.cz>
Reviewed-by: Thorsten Leemhuis <linux@leemhuis.info>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20240328194342.11760-2-balejk@matfyz.cz

authored by

Karel Balej and committed by
Jonathan Corbet 9e66f74c 1e596d5e

+6 -6
+5 -5
Documentation/admin-guide/reporting-regressions.rst
··· 42 42 -------------------- 43 43 44 44 45 - What is a "regression" and what is the "no regressions rule"? 45 + What is a "regression" and what is the "no regressions" rule? 46 46 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 47 47 48 48 It's a regression if some application or practical use case running fine with 49 49 one Linux kernel works worse or not at all with a newer version compiled using a 50 - similar configuration. The "no regressions rule" forbids this to take place; if 50 + similar configuration. The "no regressions" rule forbids this to take place; if 51 51 it happens by accident, developers that caused it are expected to quickly fix 52 52 the issue. 53 53 ··· 173 173 ------------------------------------ 174 174 175 175 176 - What is the goal of the "no regressions rule"? 176 + What is the goal of the "no regressions" rule? 177 177 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 178 178 179 179 Users should feel safe when updating kernel versions and not have to worry ··· 199 199 turned out to be wrong when they assumed a particular situation was warranting 200 200 an exception. 201 201 202 - Who ensures the "no regressions" is actually followed? 203 - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 202 + Who ensures the "no regressions" rule is actually followed? 203 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 204 204 205 205 The subsystem maintainers should take care of that, which are watched and 206 206 supported by the tree maintainers -- e.g. Linus Torvalds for mainline and
+1 -1
Documentation/process/handling-regressions.rst
··· 284 284 Check out Documentation/admin-guide/reporting-regressions.rst, it covers a lot 285 285 of other aspects you want might want to be aware of: 286 286 287 - * the purpose of the "no regressions rule" 287 + * the purpose of the "no regressions" rule 288 288 289 289 * what issues actually qualify as regression 290 290