summaryrefslogtreecommitdiff
path: root/Documentation/process
diff options
context:
space:
mode:
authorDan Carpenter <dan.carpenter@oracle.com>2016-11-28 17:43:15 +0300
committerJonathan Corbet <corbet@lwn.net>2016-11-29 03:24:32 +0300
commit388f9b20f98d4792f72091acac5031a99370827d (patch)
tree7b676a54ff124d6fdc31b79c8b3e867fa705a2d4 /Documentation/process
parent9c240d757658a3ae9968dd309e674c61f07c7f48 (diff)
downloadlinux-388f9b20f98d4792f72091acac5031a99370827d.tar.xz
Documentation/process/howto: Only send regression fixes after -rc1
The original text was not clear if white space or other harmless patches should be merged in -rc kernels. The discussion at Kernel Summit said that we should be more strict about sending regression fixes only. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/process')
-rw-r--r--Documentation/process/howto.rst19
1 files changed, 10 insertions, 9 deletions
diff --git a/Documentation/process/howto.rst b/Documentation/process/howto.rst
index 449ca1f199f4..1260f60d4cb9 100644
--- a/Documentation/process/howto.rst
+++ b/Documentation/process/howto.rst
@@ -267,15 +267,16 @@ process is as follows:
is using git (the kernel's source management tool, more information
can be found at https://git-scm.com/) but plain patches are also just
fine.
- - After two weeks a -rc1 kernel is released it is now possible to push
- only patches that do not include new features that could affect the
- stability of the whole kernel. Please note that a whole new driver
- (or filesystem) might be accepted after -rc1 because there is no
- risk of causing regressions with such a change as long as the change
- is self-contained and does not affect areas outside of the code that
- is being added. git can be used to send patches to Linus after -rc1
- is released, but the patches need to also be sent to a public
- mailing list for review.
+ - After two weeks a -rc1 kernel is released and the focus is on making the
+ new kernel as rock solid as possible. Most of the patches at this point
+ should fix a regression. Bugs that have always existed are not
+ regressions, so only push these kinds of fixes if they are important.
+ Please note that a whole new driver (or filesystem) might be accepted
+ after -rc1 because there is no risk of causing regressions with such a
+ change as long as the change is self-contained and does not affect areas
+ outside of the code that is being added. git can be used to send
+ patches to Linus after -rc1 is released, but the patches need to also be
+ sent to a public mailing list for review.
- A new -rc is released whenever Linus deems the current git tree to
be in a reasonably sane state adequate for testing. The goal is to
release a new -rc kernel every week.