From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2013.10 released
Date: Wed, 16 Oct 2013 17:34:20 -0500 [thread overview]
Message-ID: <1381962860.7979.768.camel@snotra.buserror.net> (raw)
In-Reply-To: <20131016195007.GA17401@bill-the-cat>
On Wed, 2013-10-16 at 15:50 -0400, Tom Rini wrote:
> The big, diffstat wise at least, change is that now instead of large
> boilerplate messages in every file about the license we use SPDX tags in
> all files to identify what license(s) apply here. And the source code
> itself got trimmed down a good bit. Thanks Wolfgang!
It looks like drivers/mtd/nand/nand_util.c was converted from "gpl v2
only, with Freescale preemptively granting permission for v2+" to just
"v2+". Was permission obtained from the other copyright holders?
-Scott
next prev parent reply other threads:[~2013-10-16 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 19:50 [U-Boot] [ANN] U-Boot v2013.10 released Tom Rini
2013-10-16 20:51 ` Wolfgang Denk
2013-10-16 22:34 ` Scott Wood [this message]
2013-10-17 12:18 ` Tom Rini
2013-10-17 16:12 ` Scott Wood
2013-10-17 5:47 ` Albert ARIBAUD
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=1381962860.7979.768.camel@snotra.buserror.net \
--to=scottwood@freescale.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