linux-kernel - Re: (Short?) merge window reminder

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] [day] [month] [year] [list]

Message-ID: <BANLkTinachR0M-cHzj3d4XmTOMWfCBASdA@mail.gmail.com>
Date:	Tue, 24 May 2011 10:09:46 -0400
From:	Jerome Glisse <j.glisse@...il.com>
To:	werner <w.landgraf@...ru>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: (Short?) merge window reminder

On Tue, May 24, 2011 at 9:40 AM, werner <w.landgraf@...ru> wrote:
> Version numbers should not be only numerology, but connected to quality or
> progress.  Comparing the situation of the 1, 2.0, 2.2, 2.4, 2.6 versions,
> since starting 2.6 , the progress of the kernel, and also the situation of
> Linux as a whole and of its use changed very.  Exactly in the last
> subversions with many new hardware modules/drivers the quality improved
> very.  At the same time, the subversions becomes too much since the last new
> version.  Thus, it's time for 2.8 or even 3.0 in order to mark this very
> improved quality and use of Linux since the start of the 2 and 2.6 versions.
>    wl
> ---

If i were to give my feeling, and i am doing it right now, i wish that
such version change to be backed with things like removal of dead code
for instance in the GPU side we would like at one point to drop non
KMS path and delete a whole bunch of files and dead API in the process
(at least that's on my bad santa list). Non KMS is in survival mode,
at this point we try to not break it but we don't give shit about it.
Bug against it are redirected to the closest black hole.

Cheers,
Jerome
--
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/