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: <200807180823.m6I8NIo27365@inv.it.uc3m.es>
Date:	Fri, 18 Jul 2008 10:23:18 +0200
From:	"Peter T. Breuer" <ptb@....it.uc3m.es>
To:	linux-kernel@...r.kernel.org
Subject: Re: From 2.4 to 2.6 to 2.7?

In article <20080717224041.GM31126@...lub.uwaterloo.ca> Lennart wrote:
> On Thu, Jul 17, 2008 at 11:05:07PM +0100, Alastair Stevens wrote:
>> Forgive me if I missed it, but I've not seen any suggestions along the lines
>> of this: how about just dropping the now-meaningless '.6' from the version
>> string and retaining the rest. In other words:
>> 
>>    2.27
>>    2.27.1
>>    ...
>>    2.28
>>    2.28.1
>>    2.28.2
>> 
>> That way you continue the series in a meaningful way, whilst reverting to a
>> neater 3-level numbering scheme again. Perhaps you could make 2.[6.]30 the
>> switchover point....

> So what makes the 6 meaningless and the 2 meaningful and worth keeping?

Nothing. Drop both.

  2.6.28 -> 2.8.0

could be a useful switch point.

> It does nothing for Linus's dislike of large numbers either.

The above does.

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