linux-kernel - 2.6.36/37 suggestion

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 for Android: free password hash cracker in your pocket

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

Message-ID: <AANLkTinv8Ktf6BeGCNo6RkAHmD3-Ey20vHF1ycy025uR@mail.gmail.com>
Date:	Thu, 29 Jul 2010 17:25:53 +0300
From:	Oleksandr Natalenko <pfactum@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: 2.6.36/37 suggestion

In reply to Ted Tso
(http://article.gmane.org/gmane.linux.kernel/1008643) I would like to
suggest kernel developers (first of all, Linus) some kind of
compromise. Let's prohibit accepting new features during 2.6.36 merge
window and accept only bugfixes until bugzilla and regression lists
are empty. For drivers subsystem you may create separate branch and
accept all changes there, then merge them into 2.6.37.

It should resolve "features vs stability" problem for now.
--
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/