public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Roger Meier <roger@bufferoverflow.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] libfdt: SPDX-License-Identifier: GPL-2.0+ BSD-2-Clause
Date: Sun, 28 Jul 2013 16:59:14 +0200	[thread overview]
Message-ID: <04e501ce8ba3$08496180$18dc2480$@bufferoverflow.ch> (raw)
In-Reply-To: <20130727221309.E066F380448@gemini.denx.de>

Hi Wolfgang

> -----Urspr?ngliche Nachricht-----
> Von: Wolfgang Denk [mailto:wd at denx.de]
> Gesendet: Sonntag, 28. Juli 2013 00:13
> An: Roger Meier
> Cc: u-boot at lists.denx.de
> Betreff: Re: [PATCH] libfdt: SPDX-License-Identifier: GPL-2.0+ BSD-2-Clause
> 
> Dear Roger,
> 
> In message <1374880358-7743-1-git-send-email-roger@bufferoverflow.ch>
> you wrote:
> > Signed-off-by: Roger Meier <roger@bufferoverflow.ch>
> > ---
> >  Licenses/README              |   13 ++++++------
> >  Licenses/bsd-2-clause.txt    |   25 ++++++++++++++++++++++
> >  lib/libfdt/fdt.c             |   47 +-----------------------------------------
> >  lib/libfdt/fdt_empty_tree.c  |   47 +-----------------------------------------
> >  lib/libfdt/fdt_ro.c          |   47 +-----------------------------------------
> >  lib/libfdt/fdt_rw.c          |   47 +-----------------------------------------
> >  lib/libfdt/fdt_strerror.c    |   47 +-----------------------------------------
> >  lib/libfdt/fdt_sw.c          |   47 +-----------------------------------------
> >  lib/libfdt/fdt_wip.c         |   47 +-----------------------------------------
> >  lib/libfdt/libfdt_internal.h |   47 +-----------------------------------------
> >  10 files changed, 40 insertions(+), 374 deletions(-)
> >  create mode 100644 Licenses/bsd-2-clause.txt
> 
> Thanks for pushing this forward.
> 
> I have but one comment:
> 
> > +BSD 2-Clause License				BSD-2-Clause	Y
> 		bsd-2-clause.txt	https://spdx.org/licenses/BSD-2-
> Clause
> 
> I don;t really like picking up the original license text from a second
> source (SPDX here) - I'd rather refer to some "original" version
> published by the creator of the license.
> 
> Maybe we can find a better URI here?
I agree, original version only we already have the SPDX Identifier.

It's a difficult task with BSD licenses and I found no original source yet.
Official information from Berkeley University:
http://ipira.berkeley.edu/
ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change

Other sources or information:
http://www.linfo.org/bsdlicense.html
http://opensource.org/licenses/BSD-2-Clause
http://www.freebsd.org/copyright/license.html

should I rebase without an URL for BSD-2-Clause as long as we have the
license in text form anyway?

> 
> 
> Except for that:
> 
> Acked-by: Wolfgang Denk <wd@denx.de>
Thanks!

-roger

  reply	other threads:[~2013-07-28 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 23:12 [U-Boot] [PATCH] libfdt: SPDX-License-Identifier: GPL-2.0+ BSD-2-Clause Roger Meier
2013-07-27 13:41 ` Rob Herring
2013-07-27 22:10   ` Wolfgang Denk
2013-07-27 22:13 ` Wolfgang Denk
2013-07-28 14:59   ` Roger Meier [this message]
2013-07-28 15:20     ` Wolfgang Denk
2013-08-19 19:37 ` Tom Rini

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='04e501ce8ba3$08496180$18dc2480$@bufferoverflow.ch' \
    --to=roger@bufferoverflow.ch \
    --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