linux-kernel - Re: [PATCH] README: Update version number reference

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]

Date:	Thu, 19 Mar 2015 14:20:14 -0700
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	Jonathan Corbet <corbet@....net>
Cc:	Yaowei Bai <bywxiaobai@....com>, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [PATCH] README: Update version number reference

On Thu, 2015-03-19 at 15:11 -0600, Jonathan Corbet wrote:
> On Tue, 24 Feb 2015 20:22:56 -0800
> Jeff Kirsher <jeffrey.t.kirsher@...el.com> wrote:
> 
> > When 4.0 is released, the README should reflect the new numbering.
> 
> OK, I've applied this because it came in first.  There were two other
> contenders, from Yaowei Bai and Josh Poimbeuf (copied) that all did
> mostly the same thing, but Josh was trying to make it
> version-independent. 
> 
> May I point something out, though?  All three of you did something
> like:
> 
> -     bzip2 -dc linux-3.X.tar.bz2 | tar xvf -
> +     bzip2 -dc linux-4.X.tar.bz2 | tar xvf -
> 
> without noticing the fact that .bz2 files haven't been available from
> kernel.org for a while.  Much less that installation from tarballs
> must
> be getting rare, and people shouldn't put them in /usr/src in any
> case.
> 
> In other words, this file is pretty crufty in quite a few ways that
> just
> tweaking the version number will not fix.  Given enough time I'll try
> to
> take a swing at it, but if anybody wants to bring it into the current
> era, that would be most welcome.

I am slammed with Intel wired Ethernet patches currently, so I do not
mind if someone else wants to wants to take the lead on this.  I like
the idea of making this version agnostic so that this type of
modification does not need to be made anytime a major version change is
made.

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)