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:   Fri, 17 Aug 2018 05:37:11 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Joe Perches <joe@...ches.com>
Cc:     Linus Torvalds <torvalds@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Christoph Hellwig <hch@....de>,
        Russell King <rmk+kernel@...linux.org.uk>,
        Rob Herring <rob.herring@...aro.org>,
        Jonas Oberg <jonas@...e.org>,
        Andrew Morton <akpm@...uxfoundation.org>,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH] license-rules.rst and LICENSES: Use only spdx version 3
 with -only and -or-later

On Thu, 16 Aug 2018 11:26:03 -0700
Joe Perches <joe@...ches.com> wrote:

> The current linux-kernel source git tree has a mixture of the deprecated
> spdx version 2 and the newer version 3 uses.
> 
> Update the process/license-rules.rst file to show only the version 3 style
> and use only the version 3 styles in LICENSES.
> 
> Add a script to update all old versions in the tree as well.
> 
> I suggest this be applied and the script be run and applied immediately
> after an -rc1.  The script could also be used at any time after the initial
> use to update any other deprecated spdx license uses.

All seems OK to me, with one question: if we're going to run the script
and fix everything up, do we really need to add that script to the tree
as well?  It seems like something we shouldn't need again.

If we *do* keep it for some reason, it needs a comment saying what it
does and why it exists.

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ