linux-kernel - Re: 2.6.19 -mm merge plans

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: <20060924185100.GA20524@elte.hu>
Date:	Sun, 24 Sep 2006 20:51:00 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Andrew Morton <akpm@...l.org>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Jeff Garzik <jeff@...zik.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19 -mm merge plans

* Linus Torvalds <torvalds@...l.org> wrote:

> I think the "big merges in the first two weeks, and a -rc1 after, and 
> no new code after that" rule has been working because it brought 
> everybody in on the same page.

yeah. I dont really support the even/odd release thing because even the 
old 1.2/1.3/2.0/2.1/2.2/2.3/2.4 scheme _always_ confused non-insiders. 
Sometimes i saw it confuse people who already understood the GPL ;-) 
Furthermore it would just dillute our version numbers to encode some 
information that "-rc1" indicates just as well. Insiders know perfectly 
well that when -rc1 is released the merge window is closed. And what 
causes -rc elongation is usually not the lack of communication towards 
users or lack of testing but the lack of fixing power ...

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