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

Date:	Tue, 24 May 2011 17:25:10 -0400
From:	Andy Lutomirski <luto@....EDU>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org, DRI <dri-devel@...ts.freedesktop.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <gregkh@...e.de>
Subject: Re: (Short?) merge window reminder

On 05/23/2011 04:33 PM, Linus Torvalds wrote:
> On Mon, May 23, 2011 at 12:20 PM, Ingo Molnar<mingo@...e.hu>  wrote:
>>
>> I really hope there's also a voice that tells you to wait until .42 before
>> cutting 3.0.0! :-)
>
> So I'm toying with 3.0 (and in that case, it really would be "3.0",
> not "3.0.0" - the stable team would get the third digit rather than
> the fourth one.
>
> But no, it wouldn't be for 42. Despite THHGTTG, I think "40" is a
> fairly nice round number.
>
> There's also the timing issue - since we no longer do version numbers
> based on features, but based on time, just saying "we're about to
> start the third decade" works as well as any other excuse.
>

I don't think year-based versions (like 2011.0 for the first 2011 
release, or maybe 2011.5 for May 2011) are pretty, but I'll make an 
argument for them anyway: it makes it easier to figure out when hardware 
ought to be supported.

So if I buy a 2014-model laptop and the coffee-making button doesn't 
work, and my favorite distro is running the 2013 kernel, then I know I 
shouldn't expect to it to work.  (Graphics drivers are probably a more 
realistic example.)

Also, when someone in my lab installs <insert ancient enterprise distro 
here> on a box that's running software I wrote that needs to support 
modern high-speed peripherals, then I can say "What?  You seriously 
expect this stuff to work on Linux 2007?  Let's install a slightly less 
stable distro from at least 2010."  This sounds a lot less nerdy than 
"What?  You seriously expect this stuff to work on Linux 2.6.27?  Let's 
install a slightly less stable distro that uses at least 2.6.36."

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