Commit 4f119255 authored by Christian Kujau's avatar Christian Kujau Committed by Borislav Petkov (AMD)

Documentation/process: Explain when tip branches get merged into mainline

Explain when tip branches get merged into mainline.
Suggested-by: default avatarBorislav Petkov <bp@alien8.de>
Signed-off-by: default avatarChristian Kujau <lists@nerdbynature.de>
Signed-off-by: default avatarBorislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/r/8a1fd8b7-9fe3-b2b5-406e-fa6f5e03e7c0@nerdbynature.de
parent f1fcbaa1
......@@ -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
^^^
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment