mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2014.10.0 released - license update patches
Date: Wed, 08 Oct 2014 19:14:37 +0200	[thread overview]
Message-ID: <1412788477.2569.7.camel@pengutronix.de> (raw)
In-Reply-To: <1412687840.20118.5.camel@ws-apr.office.loc>

Am Dienstag, den 07.10.2014, 15:17 +0200 schrieb Andreas Pretzsch:
> On Do, 2014-10-02 at 15:14 +0200, Michael Olbrich wrote:
> > And a rather large stack of patches that
> > add license information to various patches.
> 
> Any reason why you did not pick up the below ones ?

Mostly because I have collected all the clear-cut cases first, missed a
few, and postponed others:

> From: 	Robert Schwebel <r.schwebel@pengutronix.de>
> 
> Subject: 	[ptxdist] [PATCH 02/36] binutils: add license information
> Date: 	Mon, 15 Sep 2014 22:18:04 +0200

The binutils version depends on the toolchain, and the license changed
from GPLv2+ to GPLv3+ some time ago. I guess a mechanism to add version
dependent license information is needed here. For now this can only be
set in the BSP, where the Toolchain version is known.

> Subject: 	[ptxdist] [PATCH 03/36] boost: add license information
> Date: 	Mon, 15 Sep 2014 22:18:05 +0200

Right, I wanted to question the Python-2.0 license.

The MIT license is listed because of the rapidxml-1.13 copy in
libs/geometry/doc/src/docutils/tools/doxygen_xml2qbk/contrib.
I didn't see any Python licensed code except the header file
boost/python/detail/python22_fixed.h, and that is from Python 2.2/2.2.1.
The python license changes (changed?) all the time, so I guess this
should be Python-2.2 or Python-2.2.1 instead.

[...]
> Subject: 	[ptxdist] [PATCH 18/36] libmd: add license information
> Date: 	Mon, 15 Sep 2014 22:18:20 +0200
>
> Subject: 	[ptxdist] [PATCH 33/36] xorg-font-alias: add license information
> Date: 	Mon, 15 Sep 2014 22:18:35 +0200
> 
> Subject: 	[ptxdist] [PATCH 34/36] xorg-font-ttf-bitstream-vera: add license information
> Date: 	Mon, 15 Sep 2014 22:18:36 +0200
> 
> Subject: 	[ptxdist] [PATCH 35/36] xorg-font-util: add license information
> Date: 	Mon, 15 Sep 2014 22:18:37 +0200
> 
> Subject: 	[ptxdist] [PATCH 36/36] xorg-fonts: add license information
> Date: 	Mon, 15 Sep 2014 22:18:38 +0200
>
> From: 	Andreas Pretzsch <apr@cn-eng.de>
> 
> Subject: 	[ptxdist] [PATCH 03/16] fontconfig: add license information
> Date: 	Sun, 28 Sep 2014 14:57:50 +0200

It is not clear to me if we want to list custom licenses each with their
own name in the license field, or if there should be some categorization
or catch-all values instead.

> Subject: 	[ptxdist] [PATCH 04/16] gcclibs: add license information
> Date: 	Sun, 28 Sep 2014 14:57:51 +0200

This suffers from the same problem as binutils.

[...]
> Subject: 	[ptxdist] [PATCH 29/36] screen: add license information
> Date: 	Mon, 15 Sep 2014 22:18:31 +0200
>
> Subject: 	[ptxdist] [PATCH] tomcat: add license information
> Date: 	Sun, 28 Sep 2014 15:31:50 +0200

I just have missed these when preparing the review branch.

regards
Philipp


-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2014-10-08 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 13:14 [ptxdist] [ANNOUNCE] PTXdist 2014.10.0 released Michael Olbrich
2014-10-07 13:17 ` [ptxdist] [ANNOUNCE] PTXdist 2014.10.0 released - license update patches Andreas Pretzsch
2014-10-08 17:14   ` Philipp Zabel [this message]

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=1412788477.2569.7.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=ptxdist@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