linux-kernel - Re: [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:	Mon, 15 Dec 2014 00:29:07 -0800
From:	Christoph Hellwig <hch@...radead.org>
To:	Kevin Cernekee <cernekee@...il.com>
Cc:	tglx@...utronix.de, bp@...en8.de, gnomes@...rguk.ukuu.org.uk,
	computersforpeace@...il.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, corbet@....net,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC 1/4] Documentation: Change policy on sending patches during
 merge window

On Sun, Dec 14, 2014 at 10:09:47PM -0800, Kevin Cernekee wrote:
> 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.

FYI, I very mich disagree with that.  Merge window isn't really special,
and patches can easily be reviewed and queued up for the next merge
window in that time.  If it said you shouldn't expect replies and not
_resend_ during the merge window that seems like a much saner policy.
--
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/