From: Christian Kujau <lists@nerdbynature.de> Date: Sat, 18 Feb 2023 21:29:44 +0000 (+0100) Subject: Documentation/process: Explain when tip branches get merged into mainline X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=4f1192559707eaa7adef307f5b9ad3a444b248f8;p=linux.git Documentation/process: Explain when tip branches get merged into mainline Explain when tip branches get merged into mainline. Suggested-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Christian Kujau <lists@nerdbynature.de> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de> Link: https://lore.kernel.org/r/8a1fd8b7-9fe3-b2b5-406e-fa6f5e03e7c0@nerdbynature.de --- diff --git a/Documentation/process/maintainer-tip.rst b/Documentation/process/maintainer-tip.rst index 178c95fd17dca..93d8a794bdfc6 100644 --- a/Documentation/process/maintainer-tip.rst +++ b/Documentation/process/maintainer-tip.rst @@ -421,6 +421,9 @@ allowing themselves a breath. Please respect that. The release candidate -rc1 is the starting point for new patches to be applied which are targeted for the next merge window. +So called _urgent_ branches will be merged into mainline during the +stabilization phase of each release. + Git ^^^