All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] COPYING: state that all contributions really are covered by this file
Date: Tue, 18 Feb 2020 12:40:31 -0600	[thread overview]
Message-ID: <b3dbaeaf-0960-1b76-e2a7-7f45962ffdd2@gmail.com> (raw)
In-Reply-To: <20200206154800.GA3754085@kroah.com>

On 2/6/20 9:48 AM, Greg Kroah-Hartman wrote:
> Explicitly state that all contributions to the kernel source tree
> really are covered under this COPYING file in case someone thought
> otherwise.  Lawyers love to be pedantic, even more so than software
> engineers at times, and this sentence makes them sleep easier.
> 
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>  COPYING | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/COPYING b/COPYING
> index da4cb28febe6..a635a38ef940 100644
> --- a/COPYING
> +++ b/COPYING
> @@ -16,3 +16,5 @@ In addition, other licenses may also apply. Please see:
>  	Documentation/process/license-rules.rst
>  
>  for more details.
> +
> +All contributions to the Linux Kernel are subject to this COPYING file.
> 

Reviewed-by: Frank Rowand <frowand.list@gmail.com>

      parent reply	other threads:[~2020-02-18 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 15:48 [PATCH] COPYING: state that all contributions really are covered by this file Greg Kroah-Hartman
2020-02-06 16:02 ` Gustavo A. R. Silva
2020-02-18 18:40 ` Frank Rowand [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b3dbaeaf-0960-1b76-e2a7-7f45962ffdd2@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.