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: <20190621062115.GA11084@kroah.com>
Date:   Fri, 21 Jun 2019 08:21:15 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     "Martin K. Petersen" <martin.petersen@...cle.com>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Christoph Hellwig <hch@....de>, Hannes Reinecke <hare@...e.com>
Subject: Re: linux-next: manual merge of the scsi tree with Linus' tree

On Thu, Jun 20, 2019 at 09:14:07PM -0400, Martin K. Petersen wrote:
> 
> James,
> 
> > There's two problems.  One is simple terminology: the
> > Documentation/process/licence-rules.rst say:
> >
> > GPL-2.0 means GPL 2 only
> > GPL-2.0+ means GPL 2 or later
> >
> > I believe RMS made a fuss about this and he finally agreed to 
> >
> > GPL-2.0-only
> > GPL-2.0-or-later
> 
> Looks like there are tons of the old style SPDX tags in the kernel. Is
> there going to be a treewide conversion to the new tag format?

Not any time soon.  Both are "valid" for us, and the tools.  We are
focusing on actually tagging all files before we worry about these two
different types of tag that mean the same thing.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ