All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Khem Raj <raj.khem@gmail.com>, Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] makedevs: Don't use COPYING.patch just to add GPL-2.0-or-later into
Date: Wed, 25 May 2022 21:29:25 +0100	[thread overview]
Message-ID: <48f575397ef6c8836aaa39409c0cee47ec92041a.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1srdMiA=HpLOTYoL0PuN4sRJXjVwNM5Q6hMR+4Vs5cJrfA@mail.gmail.com>

On Wed, 2022-05-25 at 12:47 -0700, Khem Raj wrote:
> On Wed, May 25, 2022 at 11:39 AM Martin Jansa
> <martin.jansa@gmail.com> wrote:
> > 
> > Should I resend this with just GPL-2.0-only (as buildroot header) and only SPDX header in source like RP did for keymaps in: https://git.openembedded.org/openembedded-core/commit/?h=master&id=17d981005a0c0c97702ad88602b7181b69bcc9eb ?
> > 
> 
> yeah that looks better to me.

Lets make it GPL-2.0-only which seems safest given the confusion and
put an SPDX-License-Identifier in the source file.

Very happy to see this cleaned up though!

Cheers,

Richard



  reply	other threads:[~2022-05-25 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16F26ACEC3C7C32B.14582@lists.openembedded.org>
2022-05-25 18:21 ` [OE-core] [PATCH] makedevs: Don't use COPYING.patch just to add GPL-2.0-or-later into Martin Jansa
2022-05-25 18:30   ` Khem Raj
2022-05-25 18:38     ` Martin Jansa
2022-05-25 19:47       ` Khem Raj
2022-05-25 20:29         ` richard.purdie [this message]
2022-05-25 21:04           ` [PATCHv2] makedevs: Don't use COPYING.patch just to add license file into ${S} Martin Jansa

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=48f575397ef6c8836aaa39409c0cee47ec92041a.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.