linux-kernel - Re: Linux 3.0-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, 14 Jun 2011 14:38:49 +0200
From:	Maarten Lankhorst <m.b.lankhorst@...il.com>
To:	Denys Vlasenko <vda.linux@...glemail.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.0-rc3

Op 14-06-11 14:15, Denys Vlasenko schreef:
> On Tue, Jun 14, 2011 at 1:01 AM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>> .. and this time even with a timely tar-ball, since I'm not traveling any more.
>>
>> What do we have in it? More than in -rc2. I'm clearly not the only one
>> who was in Japan for LinuxCon, or something else just made people wake
>> up.
> Linus, I know I run a risk of being not the first person to ask this,
> but anyway.
>
> I've got a patch for my project to fix parsing of kernel version which
> has only two numbers. Basically,
>
> - scanf(ver, "%u.%u.%u", &a, &b, &c)
> + sscanf(ver, "%u.%u", &a, &b)
>
> I can take it, but it made me thinking: how many other projects
> will be similarly affected? Must be hundreds, even thousands.
>
> I propose to still use three digits. I mean, if you want to use
> 3.0, 3.1, 3.2 numbering for your releases and leave third digit
> for stable series, just number them 3.0.0, 3.1.0, 3.2.0 instead.
>
> This way, many userspace projects will need less patching
> in order to work with 3.x. In many cases, they can
> avoid patching altogether.
>
~$ uname -r
3.0.0-rc3-patser+

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