linux-kernel - Re: Linux 2.6.32-rc3

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, 6 Oct 2009 08:13:18 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dirk Hohndel <hohndel@...radead.org>
cc:	Len Brown <lenb@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.32-rc3

On Tue, 6 Oct 2009, Dirk Hohndel wrote:
> 
> I respectfully disagree.

.. because you don't know what the f*ck you're talking about.

> With the proposed -rc0 there is EXACTLY ONE kernel that is called 2.6.31
> - the release kernel. And everything else is called something
> 2.6.xx-rcY.

No.

That's simply not _true_.

Think it through. Deeply. 

In particular, think about all the developers who start out at known 
stable points. And they are _supposed_ to start at release points. It 
means that a lot of versions in the -rc window will NOT have that -rc0 in 
them.

In fact, even more commonly (for people who don't rebase, which should be 
the default), you'll have kernel versions in the merge window (and later) 
that will have Makefiles that talk about the previous release.

If you can't get that FUNDAMENTAL FACT, then I don't know what to say.

> So if you see something that identifies itself as -rc0, you know it's
> from during the merge window. If you see something that calls itself
> 2.6.xx then you know it's a release kernel.

No. No. And NO.

Your kind of magical thinking leads to _problems_. It's literally been a 
problem that people stop bisecting, because they notice that they start 
testing kernels that have a version number before the release they already 
tested as good. Exactly because of your kind of linear thinking.

We need _less_ linear thinking, not more. And you need to start thinking 
about other kernels than just my release tree.

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