public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPDX License status
Date: Fri, 25 Aug 2017 09:46:00 +0200	[thread overview]
Message-ID: <20170825074600.7CC5F120450@gemini.denx.de> (raw)
In-Reply-To: <20170825012557.GK2827@bill-the-cat>

Dear Tom,

In message <20170825012557.GK2827@bill-the-cat> you wrote:
> 
> Actual code we have to take care with anyhow, but it's still up to the
> person that has to handle the syncing.

Really?  Should we not rather implement a common, consistent policy
for the whole project?

Our patch submission already include a rule for new code [1]:

        If you add new files, please always make sure that these
        contain your copyright note and a GPLv2+
        SPDX-License-Identifier, for example like this:

	(C) Copyright 2010  Joe Hacker <jh@hackers.paradise.com>

	SPDX-License-Identifier:	GPL-2.0+

Should we not ask the same for code merged from other projects?

[1] Bullet #3 in http://www.denx.de/wiki/view/U-Boot/Patches#Attributing_Code_Copyrights_Sign

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
On mules we find two legs behind and two we find before.
We stand behind before we find what those behind be for.

  reply	other threads:[~2017-08-25  7:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  8:09 [U-Boot] SPDX License status Wolfgang Denk
2017-08-19  1:15 ` Tom Rini
2017-08-21 15:25   ` Wolfgang Denk
2017-08-21 19:23     ` Tom Rini
2017-08-22  8:39       ` Wolfgang Denk
2017-08-25  1:25         ` Tom Rini
2017-08-25  7:46           ` Wolfgang Denk [this message]
2017-11-02 18:25             ` Masahiro Yamada

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=20170825074600.7CC5F120450@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.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