From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPDX-License-Identifier on new files
Date: Fri, 11 Oct 2013 14:47:14 -0400 [thread overview]
Message-ID: <20131011184714.GQ15917@bill-the-cat> (raw)
In-Reply-To: <CAOg16C+xNXgjXQZdhXurUfOSzhWb6VSSuy=5ch3YdOfdkCJuOA@mail.gmail.com>
On Fri, Oct 11, 2013 at 11:07:58AM -0700, D Rambo wrote:
> Is there a policy that new source files upstreamed to u-boot contain
> registered SPDX license identifiers? I see that there are still about 1900
> source files that have no SPDX identifier, and about 6000 that do. The
> reason I'm asking is that our company has a dual license (for GPL2.0 or
> Proprietary), and would like to know if it is possible to submit code that
> has the legacy dual license first (and register/clean up SPDX later), or if
> we need to do the internal legal and register the appropriate licenses with
> spdx.org first before submission upstream?
New code needs to use SPDX tags.
Next, I'm not a lawyer but you should ask the legal folks in your
company if you can't just license a copy of the code in question you
want to use as reference as GPL-2.0
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131011/c040ff9a/attachment.pgp>
next prev parent reply other threads:[~2013-10-11 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 18:07 [U-Boot] SPDX-License-Identifier on new files D Rambo
2013-10-11 18:47 ` Tom Rini [this message]
2013-10-11 21:57 ` Wolfgang Denk
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=20131011184714.GQ15917@bill-the-cat \
--to=trini@ti.com \
--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