mailarchive of the pengutronix oss-tools mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: oss-tools@pengutronix.de, Roland Hieber <rhi@pengutronix.de>
Subject: Re: [OSS-Tools] [PATCH dt-utils 1/4] treewide: add SPDX identifiers to files with GPL-2.0-or-later license
Date: Tue, 30 Mar 2021 15:30:40 +0200	[thread overview]
Message-ID: <20210330133040.srgjieqjojrgkaio@pengutronix.de> (raw)
In-Reply-To: <2fee9810-d20a-dea2-9eb8-9fd5c2ef07f0@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]

Hello,

On Tue, Mar 30, 2021 at 01:22:26PM +0200, Ahmad Fatoum wrote:
> On 30.03.21 13:08, Roland Hieber wrote:
> > Uwe, could I get a Reviewed-by from you for these four patches? :-)
> 
> We must still carry the full license texts in the project (cf. Linux
> LICENSES/). This is missing here, no?

well, it depends on what you want to achieve. If you want to become SPDX
conformant this is indeed necessary. IMHO the conversion from several
different boilerplate license specifications to a single line is
beneficial even if the full licenses are not (yet) in the project.

So I don't regret having given my Review-tags.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 96 bytes --]

_______________________________________________
OSS-Tools mailing list
OSS-Tools@pengutronix.de

  reply	other threads:[~2021-03-30 13:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 21:06 Roland Hieber
2021-03-26 21:06 ` [OSS-Tools] [PATCH dt-utils 2/4] treewide: add SPDX identifiers to files with GPL-2.0-only license Roland Hieber
2021-03-30 12:50   ` Uwe Kleine-König
2021-03-26 21:06 ` [OSS-Tools] [PATCH dt-utils 3/4] treewide: add SPDX identifier to files with Zlib license Roland Hieber
2021-03-30 12:55   ` Uwe Kleine-König
2021-03-26 21:06 ` [OSS-Tools] [PATCH dt-utils 4/4] treewide: add SPDX identifiers to files without license Roland Hieber
2021-03-30 11:08 ` [OSS-Tools] [PATCH dt-utils 1/4] treewide: add SPDX identifiers to files with GPL-2.0-or-later license Roland Hieber
2021-03-30 11:22   ` Ahmad Fatoum
2021-03-30 13:30     ` Uwe Kleine-König [this message]
2021-03-30 13:50       ` Ahmad Fatoum
2021-03-30 14:00         ` Uwe Kleine-König
2021-03-30 14:04           ` Ahmad Fatoum
2021-03-30 15:53         ` Roland Hieber
2021-03-30 17:31           ` Ahmad Fatoum
2021-03-31 10:03             ` Roland Hieber
2021-03-31 10:10               ` Roland Hieber
2021-03-30 12:49 ` Uwe Kleine-König
2023-08-01 10:10 ` Roland Hieber
2023-08-01 10:12   ` Roland Hieber

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=20210330133040.srgjieqjojrgkaio@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=oss-tools@pengutronix.de \
    --cc=rhi@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox