On Fri, Feb 9, 2018 at 1:35 AM, Joe Perches wrote:
> On Fri, 2018-02-02 at 13:18 -0800, Joe Perches wrote:
>> On Fri, 2018-02-02 at 09:40 -0600, Rob Herring wrote:
>> > Add SPDX license tag check based on the rules defined in
>> > Documentation/process/license-rules.rst. To
On Fri, Feb 9, 2018 at 1:35 AM, Joe Perches wrote:
> On Fri, 2018-02-02 at 13:18 -0800, Joe Perches wrote:
>> On Fri, 2018-02-02 at 09:40 -0600, Rob Herring wrote:
>> > Add SPDX license tag check based on the rules defined in
>> > Documentation/process/license-rules.rst. To summarize, SPDX
On Fri, 2018-02-02 at 13:18 -0800, Joe Perches wrote:
> On Fri, 2018-02-02 at 09:40 -0600, Rob Herring wrote:
> > Add SPDX license tag check based on the rules defined in
> > Documentation/process/license-rules.rst. To summarize, SPDX license tags
> > should be on the 1st line (or 2nd line in
On Fri, 2018-02-02 at 13:18 -0800, Joe Perches wrote:
> On Fri, 2018-02-02 at 09:40 -0600, Rob Herring wrote:
> > Add SPDX license tag check based on the rules defined in
> > Documentation/process/license-rules.rst. To summarize, SPDX license tags
> > should be on the 1st line (or 2nd line in
Joe,
On Thu, Feb 8, 2018 at 6:24 PM, Joe Perches wrote:
> On Thu, 2018-02-08 at 15:35 +0100, Philippe Ombredanne wrote:
>> However checking that licenses ids are known and listed in the kernel
>> doc is essential IMHO to avoid drift and insulate the kernel from SPDX
>> updates.
Joe,
On Thu, Feb 8, 2018 at 6:24 PM, Joe Perches wrote:
> On Thu, 2018-02-08 at 15:35 +0100, Philippe Ombredanne wrote:
>> However checking that licenses ids are known and listed in the kernel
>> doc is essential IMHO to avoid drift and insulate the kernel from SPDX
>> updates. Case in point
On Thu, 2018-02-08 at 15:35 +0100, Philippe Ombredanne wrote:
> However checking that licenses ids are known and listed in the kernel
> doc is essential IMHO to avoid drift and insulate the kernel from SPDX
> updates. Case in point the new SPDX "GPL-2.0-only" is NOT what was
> documented by tglx
On Thu, 2018-02-08 at 15:35 +0100, Philippe Ombredanne wrote:
> However checking that licenses ids are known and listed in the kernel
> doc is essential IMHO to avoid drift and insulate the kernel from SPDX
> updates. Case in point the new SPDX "GPL-2.0-only" is NOT what was
> documented by tglx
On Sat, Feb 3, 2018 at 2:41 PM, Igor Stoppa wrote:
>
>
> On 02/02/18 21:06, Joe Perches wrote:
>> On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
>>> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
On 02/02/18 17:40, Rob Herring
On Sat, Feb 3, 2018 at 2:41 PM, Igor Stoppa wrote:
>
>
> On 02/02/18 21:06, Joe Perches wrote:
>> On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
>>> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
On 02/02/18 17:40, Rob Herring wrote:
> Add SPDX license tag check based on the
Kate,
On Fri, Feb 2, 2018 at 9:18 PM, Kate Stewart
wrote:
> This is the new way to represent GPLv2 only, as described above.
> While the GPL-2.0 and GPL-2.0+ notation is still valid, it is deprecated
> in the latest version, so transitioning existing over time will
Kate,
On Fri, Feb 2, 2018 at 9:18 PM, Kate Stewart
wrote:
> This is the new way to represent GPLv2 only, as described above.
> While the GPL-2.0 and GPL-2.0+ notation is still valid, it is deprecated
> in the latest version, so transitioning existing over time will probably
> be needed. So I
even
On Fri, Feb 2, 2018 at 8:06 PM, Joe Perches wrote:
> On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
>> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
>> > On 02/02/18 17:40, Rob Herring wrote:
>> > > Add SPDX license tag check based on
even
On Fri, Feb 2, 2018 at 8:06 PM, Joe Perches wrote:
> On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
>> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
>> > On 02/02/18 17:40, Rob Herring wrote:
>> > > Add SPDX license tag check based on the rules defined in
>> >
>> > Shouldn't it
On 02/02/18 21:06, Joe Perches wrote:
> On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
>> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
>>> On 02/02/18 17:40, Rob Herring wrote:
Add SPDX license tag check based on the rules defined in
>>>
>>> Shouldn't
On 02/02/18 21:06, Joe Perches wrote:
> On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
>> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
>>> On 02/02/18 17:40, Rob Herring wrote:
Add SPDX license tag check based on the rules defined in
>>>
>>> Shouldn't it also check that the
On Fri, 2018-02-02 at 09:40 -0600, Rob Herring wrote:
> Add SPDX license tag check based on the rules defined in
> Documentation/process/license-rules.rst. To summarize, SPDX license tags
> should be on the 1st line (or 2nd line in scripts) using the appropriate
> comment style for the file type.
On Fri, 2018-02-02 at 09:40 -0600, Rob Herring wrote:
> Add SPDX license tag check based on the rules defined in
> Documentation/process/license-rules.rst. To summarize, SPDX license tags
> should be on the 1st line (or 2nd line in scripts) using the appropriate
> comment style for the file type.
On Fri, 2018-02-02 at 14:57 -0600, Rob Herring wrote:
> On Fri, Feb 2, 2018 at 1:06 PM, Joe Perches wrote:
[]
> > Right now, there are many missing licenses
> > that are already used by various existing
> > SPDX-License-Identifier: entries.
> >
> > APACHE-2.0
>
> Given that
On Fri, 2018-02-02 at 14:57 -0600, Rob Herring wrote:
> On Fri, Feb 2, 2018 at 1:06 PM, Joe Perches wrote:
[]
> > Right now, there are many missing licenses
> > that are already used by various existing
> > SPDX-License-Identifier: entries.
> >
> > APACHE-2.0
>
> Given that Apache 2.0 is not
On Fri, Feb 2, 2018 at 1:06 PM, Joe Perches wrote:
> On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
>> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
>> > On 02/02/18 17:40, Rob Herring wrote:
>> > > Add SPDX license tag check based on the
On Fri, Feb 2, 2018 at 1:06 PM, Joe Perches wrote:
> On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
>> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
>> > On 02/02/18 17:40, Rob Herring wrote:
>> > > Add SPDX license tag check based on the rules defined in
>> >
>> > Shouldn't it also
On Fri, 2018-02-02 at 14:18 -0600, Kate Stewart wrote:
> On Fri, Feb 2, 2018 at 1:06 PM, Joe Perches wrote:
>
> > On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
> > > On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa
> >
> > wrote:
> > > > On 02/02/18
On Fri, 2018-02-02 at 14:18 -0600, Kate Stewart wrote:
> On Fri, Feb 2, 2018 at 1:06 PM, Joe Perches wrote:
>
> > On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
> > > On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa
> >
> > wrote:
> > > > On 02/02/18 17:40, Rob Herring wrote:
> > > > > Add
On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
> > On 02/02/18 17:40, Rob Herring wrote:
> > > Add SPDX license tag check based on the rules defined in
> >
> > Shouldn't it also check that the license is
On Fri, 2018-02-02 at 12:27 -0600, Rob Herring wrote:
> On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
> > On 02/02/18 17:40, Rob Herring wrote:
> > > Add SPDX license tag check based on the rules defined in
> >
> > Shouldn't it also check that the license is compatible?
> >
>
> Perhaps we
On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
> On 02/02/18 17:40, Rob Herring wrote:
>> Add SPDX license tag check based on the rules defined in
>
> Shouldn't it also check that the license is compatible?
>
Perhaps we shouldn't try to script legal advice.
> [...]
>
On Fri, Feb 2, 2018 at 9:49 AM, Igor Stoppa wrote:
> On 02/02/18 17:40, Rob Herring wrote:
>> Add SPDX license tag check based on the rules defined in
>
> Shouldn't it also check that the license is compatible?
>
Perhaps we shouldn't try to script legal advice.
> [...]
>
>> +
On Fri, 2 Feb 2018 17:12:46 +0100
Greg Kroah-Hartman wrote:
> > What is the correct/acceptable license for documentation?
> > Creative Commons? AFAIK GPL is for source code.
> >
> > Googling didn't bring the wished-for enlightenment.
>
> It depends on what you
On Fri, 2 Feb 2018 17:12:46 +0100
Greg Kroah-Hartman wrote:
> > What is the correct/acceptable license for documentation?
> > Creative Commons? AFAIK GPL is for source code.
> >
> > Googling didn't bring the wished-for enlightenment.
>
> It depends on what you want to allow the documentation
On Fri, Feb 02, 2018 at 05:49:20PM +0200, Igor Stoppa wrote:
> On 02/02/18 17:40, Rob Herring wrote:
> > Add SPDX license tag check based on the rules defined in
>
> Shouldn't it also check that the license is compatible?
Baby steps please :)
> [...]
>
> > + } elsif
On Fri, Feb 02, 2018 at 05:49:20PM +0200, Igor Stoppa wrote:
> On 02/02/18 17:40, Rob Herring wrote:
> > Add SPDX license tag check based on the rules defined in
>
> Shouldn't it also check that the license is compatible?
Baby steps please :)
> [...]
>
> > + } elsif
On 02/02/18 17:40, Rob Herring wrote:
> Add SPDX license tag check based on the rules defined in
Shouldn't it also check that the license is compatible?
[...]
> + } elsif ($realfile =~ /\.rst$/) {
> + $comment = '..';
What is the
On 02/02/18 17:40, Rob Herring wrote:
> Add SPDX license tag check based on the rules defined in
Shouldn't it also check that the license is compatible?
[...]
> + } elsif ($realfile =~ /\.rst$/) {
> + $comment = '..';
What is the
Add SPDX license tag check based on the rules defined in
Documentation/process/license-rules.rst. To summarize, SPDX license tags
should be on the 1st line (or 2nd line in scripts) using the appropriate
comment style for the file type.
Cc: Andy Whitcroft
Cc: Joe Perches
Add SPDX license tag check based on the rules defined in
Documentation/process/license-rules.rst. To summarize, SPDX license tags
should be on the 1st line (or 2nd line in scripts) using the appropriate
comment style for the file type.
Cc: Andy Whitcroft
Cc: Joe Perches
Cc: Thomas Gleixner
Cc:
36 matches
Mail list logo