Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Tue, Jun 12, 2018 at 2:27 PM, Thomas Gleixner wrote: > Yang, > > On Tue, 12 Jun 2018, Yang Li wrote: >> On Thu, Dec 28, 2017 at 4:17 PM, Thomas Gleixner wrote: >> > On Thu, 28 Dec 2017, Thomas Gleixner wrote: >> > >> > Sorry for the spam. I somehow missed to refresh the patch before

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Tue, Jun 12, 2018 at 2:27 PM, Thomas Gleixner wrote: > Yang, > > On Tue, 12 Jun 2018, Yang Li wrote: >> On Thu, Dec 28, 2017 at 4:17 PM, Thomas Gleixner wrote: >> > On Thu, 28 Dec 2017, Thomas Gleixner wrote: >> > >> > Sorry for the spam. I somehow missed to refresh the patch before

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

Yang, On Tue, 12 Jun 2018, Yang Li wrote: > On Thu, Dec 28, 2017 at 4:17 PM, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > > > Sorry for the spam. I somehow missed to refresh the patch before generating > > the mbox. Find below the correct version of that one which

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

Yang, On Tue, 12 Jun 2018, Yang Li wrote: > On Thu, Dec 28, 2017 at 4:17 PM, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > > > Sorry for the spam. I somehow missed to refresh the patch before generating > > the mbox. Find below the correct version of that one which

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Thu, Dec 28, 2017 at 4:17 PM, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > Sorry for the spam. I somehow missed to refresh the patch before generating > the mbox. Find below the correct version of that one which has ALL braces > removed which we don't need. Hi

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Thu, Dec 28, 2017 at 4:17 PM, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > Sorry for the spam. I somehow missed to refresh the patch before generating > the mbox. Find below the correct version of that one which has ALL braces > removed which we don't need. Hi

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Thu, Dec 28, 2017 at 04:27:11PM +0100, Thomas Gleixner wrote: > Add a file to the Documentation directory to describe how file licenses > should be described in all kernel files, using the SPDX identifier, as well > as where all licenses should be in the kernel source tree for people to > refer

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Thu, Dec 28, 2017 at 04:27:11PM +0100, Thomas Gleixner wrote: > Add a file to the Documentation directory to describe how file licenses > should be described in all kernel files, using the SPDX identifier, as well > as where all licenses should be in the kernel source tree for people to > refer

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Dec 29, 2017, at 9:15 PM, Theodore Ts'o wrote: > > On Fri, Dec 29, 2017 at 11:17:54PM +0100, Philippe Ombredanne wrote: >>> As far as I know, none of the licenses explicitly say >>> copyright license must be on each file. Just that the distribution of >>> source must include

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Dec 29, 2017, at 9:15 PM, Theodore Ts'o wrote: > > On Fri, Dec 29, 2017 at 11:17:54PM +0100, Philippe Ombredanne wrote: >>> As far as I know, none of the licenses explicitly say >>> copyright license must be on each file. Just that the distribution of >>> source must include the copyright

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, 29 Dec 2017, Theodore Ts'o wrote: > On Fri, Dec 29, 2017 at 08:19:59AM -0800, Joe Perches wrote: > > > > Has it been legally reviewed and accepted that removal > > of the BSD license text from individual source files is > > appropriate and meets the legal requirements of > > following the

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, 29 Dec 2017, Theodore Ts'o wrote: > On Fri, Dec 29, 2017 at 08:19:59AM -0800, Joe Perches wrote: > > > > Has it been legally reviewed and accepted that removal > > of the BSD license text from individual source files is > > appropriate and meets the legal requirements of > > following the

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, Dec 29, 2017 at 11:17:54PM +0100, Philippe Ombredanne wrote: > > As far as I know, none of the licenses explicitly say > > copyright license must be on each file. Just that the distribution of > > source must include the copyright and license statement. Exactly how > > that is done is

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, Dec 29, 2017 at 11:17:54PM +0100, Philippe Ombredanne wrote: > > As far as I know, none of the licenses explicitly say > > copyright license must be on each file. Just that the distribution of > > source must include the copyright and license statement. Exactly how > > that is done is

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, Dec 29, 2017 at 7:54 PM, Theodore Ts'o wrote: > On Fri, Dec 29, 2017 at 08:19:59AM -0800, Joe Perches wrote: >> >> Has it been legally reviewed and accepted that removal >> of the BSD license text from individual source files is >> appropriate and meets the legal

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, Dec 29, 2017 at 7:54 PM, Theodore Ts'o wrote: > On Fri, Dec 29, 2017 at 08:19:59AM -0800, Joe Perches wrote: >> >> Has it been legally reviewed and accepted that removal >> of the BSD license text from individual source files is >> appropriate and meets the legal requirements of >>

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, Dec 29, 2017 at 08:19:59AM -0800, Joe Perches wrote: > > Has it been legally reviewed and accepted that removal > of the BSD license text from individual source files is > appropriate and meets the legal requirements of > following the BSD license on a per-file basis? > > And if so, who

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, Dec 29, 2017 at 08:19:59AM -0800, Joe Perches wrote: > > Has it been legally reviewed and accepted that removal > of the BSD license text from individual source files is > appropriate and meets the legal requirements of > following the BSD license on a per-file basis? > > And if so, who

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, 2017-12-29 at 14:21 +0100, Philippe Ombredanne wrote: > Thomas, > > On Thu, Dec 28, 2017 at 11:17 PM, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > > > Sorry for the spam. I somehow missed to refresh the patch before generating > > the

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Fri, 2017-12-29 at 14:21 +0100, Philippe Ombredanne wrote: > Thomas, > > On Thu, Dec 28, 2017 at 11:17 PM, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > > > Sorry for the spam. I somehow missed to refresh the patch before generating > > the mbox. Find below the

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

Thomas, On Thu, Dec 28, 2017 at 11:17 PM, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > Sorry for the spam. I somehow missed to refresh the patch before generating > the mbox. Find below the correct version of that one which has ALL braces > removed

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

Thomas, On Thu, Dec 28, 2017 at 11:17 PM, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > Sorry for the spam. I somehow missed to refresh the patch before generating > the mbox. Find below the correct version of that one which has ALL braces > removed which we don't

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Thu, 28 Dec 2017, Thomas Gleixner wrote: Sorry for the spam. I somehow missed to refresh the patch before generating the mbox. Find below the correct version of that one which has ALL braces removed which we don't need. Thanks, tglx 8<-- Subject:

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Thu, 28 Dec 2017, Thomas Gleixner wrote: Sorry for the spam. I somehow missed to refresh the patch before generating the mbox. Find below the correct version of that one which has ALL braces removed which we don't need. Thanks, tglx 8<-- Subject:

[patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

Add a file to the Documentation directory to describe how file licenses should be described in all kernel files, using the SPDX identifier, as well as where all licenses should be in the kernel source tree for people to refer to (LICENSES/). Thanks to Kate and Greg for review and editing and

[patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

Add a file to the Documentation directory to describe how file licenses should be described in all kernel files, using the SPDX identifier, as well as where all licenses should be in the kernel source tree for people to refer to (LICENSES/). Thanks to Kate and Greg for review and editing and