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: <960e6632bb6c9e45845e9078af6dd5939cd3bea6.camel@perches.com>
Date:   Fri, 17 Aug 2018 09:02:15 -0700
From:   Joe Perches <joe@...ches.com>
To:     Jonathan Corbet <corbet@....net>
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 Fri, 2018-08-17 at 05:37 -0600, Jonathan Corbet wrote:
> 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.

linux-next has other files with licenses that would need to be
updated even after an -rc1

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ