linux-kernel - [RFC 1/4] Documentation: Change policy on sending patches during merge window

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 14 Dec 2014 22:09:47 -0800
From:	Kevin Cernekee <cernekee@...il.com>
To:	tglx@...utronix.de, bp@...en8.de, gnomes@...rguk.ukuu.org.uk
Cc:	computersforpeace@...il.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, corbet@....net,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC 1/4] Documentation: Change policy on sending patches during merge window

Ask patch submitters to avoid sending non-critical patches when the
merge window is open.  This basically extends the net-next policy in
netdev-FAQ.txt to the entire kernel.

Suggested-by: Thomas Gleixner <tglx@...utronix.de>
Signed-off-by: Kevin Cernekee <cernekee@...il.com>
---
 Documentation/development-process/5.Posting | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/Documentation/development-process/5.Posting b/Documentation/development-process/5.Posting
index 8a48c9b..14f8b01 100644
--- a/Documentation/development-process/5.Posting
+++ b/Documentation/development-process/5.Posting
@@ -26,6 +26,15 @@ which remains to be done and any known problems.  Fewer people will look at
 patches which are known to be half-baked, but those who do will come in
 with the idea that they can help you drive the work in the right direction.
 
+Some maintainers prefer to receive only urgent patches when the merge
+window is open, so that critical fixes do not get lost in the noise during
+times of peak activity.  If you are posting an actual [PATCH] (not something
+that is obviously low-priority such as an [RFC] or [RANT]) and you aren't sure
+of your maintainer's stance, the safest thing to do is hold off until the
+merge window has closed.  You can visit https://www.kernel.org/ to check
+the merge window status; it is closed if the "mainline:" entry shows a
+version number containing "-rc", and open if a non-rc version number appears.
+
 
 5.2: BEFORE CREATING PATCHES
 
-- 
2.1.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/