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

Message ID bd85b781-c5a5-0dbe-f353-5b87a2de26bd@nerdbynature.de
State New
Headers
Series Documentation/process: Explain when tip branches get merged into mainline |

Commit Message

Christian Kujau Feb. 18, 2023, 9:29 p.m. UTC
  Explain when tip branches get merged into mainline.
    
Signed-off-by: Christian Kujau <lists@nerdbynature.de>
Suggested-by: Borislav Petkov <bp@alien8.de>

---
  

Patch

diff --git a/Documentation/process/maintainer-tip.rst b/Documentation/process/maintainer-tip.rst
index 572a3289c9cb..d43cc2272e83 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
 ^^^