linux-kernel - Re: From 2.4 to 2.6 to 2.7?

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: <200807191930.m6JJURC12038@inv.it.uc3m.es>
Date:	Sat, 19 Jul 2008 21:30:27 +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 <20080719080002.GA11272@....edu> you wrote:
> In <200807180823.m6I8NIo27365@....it.uc3m.es>, Peter T. Breuer
> proposed switching to a three-level numbering scheme and resetting the
> middle number when useful [which I suppose might mean a major feature
> change or just a desire to avoid largish meaningless numbers].  I
> assume this sould give a sequence like:

> 2.6.26.s, 2.8.s, 2.9.s, 2.10.s,

Actually he said

   rename 2.6.28 to 2.8.0
or 
   rename 2.6.29 to 2.9.0
or
   rename 2.6.30 to 3.0.0

i.e. .. whatever you are doing now, just drop the first two numbers (the
"2.6" bit) since they seem to be constant.

I don't know where the idea you propose above came from, and I don't
quite understand it either!

Remember that Linus' only objective is to have smaller numbers, which
may therefore

 1) be memorable
 2) be good advertising copy
 3) be meaningful

and that was the only intention of my scheme: "drop the constant bit".

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/