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: <alpine.LRH.1.10.0810190114420.2000@twin.jikos.cz>
Date:	Sun, 19 Oct 2008 01:17:19 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Willy Tarreau <w@....eu>
cc:	Greg KH <greg@...ah.com>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Steven Noonan <steven@...inklabs.net>,
	Adrian Bunk <bunk@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] Kernel version numbering scheme change

On Sat, 18 Oct 2008, Willy Tarreau wrote:

> confusion between 2.4.37 and 2.6.27. I have already tagged kernels with 
> wrong versions, having to fix by hand afterwards. It's really cumbersome 
> some times.

But this is only because you are maintaining a source code that is several 
years old, right? Would maintaining a series numbered 2002.x.y make your 
situation a lot better? Do you think you'd never make typo '2002 instead 
of 2006' any more?

Or how would you distingiush the kernel tree you are maintaing from the 
one Linus is maintaining?

-- 
Jiri Kosina
SUSE Labs

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ