linux-kernel - Re: [RFC 0/4] Stop maintainer abuse

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]

Message-ID: <20141216130939.166c4369@lwn.net>
Date:	Tue, 16 Dec 2014 13:09:39 -0500
From:	Jonathan Corbet <corbet@....net>
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, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/4] Stop maintainer abuse

On Sun, 14 Dec 2014 22:09:46 -0800
Kevin Cernekee <cernekee@...il.com> wrote:

> This patch series amends the kernel development process to reduce the
> load on key maintainers during peak periods, by discouraging the submission
> of non-urgent patches while the merge window is open.

You do understand the irony of posting this during the merge window,
right? :)

In general, I worry about trying to codify things too much just because
different maintainers have different expectations.  As Linus noted, some
maintainers have their work done by the time the merge window starts and
can take patches just fine — until something catches fire, at least.

I'll await a revision taking account the feedback you've gotten, just
adding my own suggestion to phrase things as guidelines rather than
hard-and-fast rules.

Thanks,

jon
--
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/