From: "tip-bot2 for Christian Kujau" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
Christian Kujau <lists@nerdbynature.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/cleanups] Documentation/process: Explain when tip branches get merged into mainline
Date: Mon, 08 May 2023 13:41:24 -0000 [thread overview]
Message-ID: <168355328495.404.278386404769420617.tip-bot2@tip-bot2> (raw)
In-Reply-To: <8a1fd8b7-9fe3-b2b5-406e-fa6f5e03e7c0@nerdbynature.de>
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: cb5d28c01b2d56700e1656cd6c3742b40e840bf9
Gitweb: https://git.kernel.org/tip/cb5d28c01b2d56700e1656cd6c3742b40e840bf9
Author: Christian Kujau <lists@nerdbynature.de>
AuthorDate: Sat, 18 Feb 2023 22:29:44 +01:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Mon, 08 May 2023 15:35:00 +02:00
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
---
Documentation/process/maintainer-tip.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/process/maintainer-tip.rst b/Documentation/process/maintainer-tip.rst
index 178c95f..93d8a79 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
^^^
next prev parent reply other threads:[~2023-05-08 13:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 3:46 External USB disks not recognized with v6.1.8 when using Xen Christian Kujau
2023-01-30 5:17 ` Greg KH
2023-01-30 12:01 ` Linux kernel regression tracking (#adding)
2023-01-31 22:50 ` Christian Kujau
2023-02-01 8:14 ` Juergen Gross
2023-02-01 9:37 ` Christian Kujau
2023-02-02 11:38 ` Christian Kujau
2023-02-02 20:24 ` Linus Torvalds
2023-02-03 16:50 ` Christian Kujau
2023-02-03 17:29 ` Christian Kujau
2023-02-05 13:20 ` Borislav Petkov
2023-02-05 17:17 ` Christian Kujau
2023-02-05 20:21 ` Linus Torvalds
2023-02-06 6:33 ` Juergen Gross
2023-02-06 9:54 ` Juergen Gross
2023-02-06 9:43 ` Borislav Petkov
2023-02-05 10:40 ` Linux kernel regression tracking (#update)
2023-02-14 9:35 ` [tip: x86/urgent] x86/mtrr: Revert 90b926e68f50 ("x86/pat: Fix pat_x_mtrr_type() for MTRR disabled case") tip-bot2 for Juergen Gross
2023-02-18 9:47 ` Christian Kujau
2023-02-18 9:59 ` Borislav Petkov
2023-05-08 13:41 ` tip-bot2 for Christian Kujau [this message]
2023-05-15 15:28 ` [tip: x86/cleanups] Documentation/process: Explain when tip branches get merged into mainline tip-bot2 for Christian Kujau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=168355328495.404.278386404769420617.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).