From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Roland Hieber <rhi@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3] python3-numpy: New package
Date: Thu, 14 Nov 2019 11:07:16 +0100 [thread overview]
Message-ID: <CABDcavZoyCCHh=Ubh15LnncCCU-P5MrBZr2PiiJPu-vXHH0zMA@mail.gmail.com> (raw)
In-Reply-To: <20191114095605.hhfgwkogkoc3xyfj@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 735 bytes --]
Hi Roland,
El jue., 14 nov. 2019 a las 10:56, Roland Hieber (<rhi@pengutronix.de>)
escribió:
> > > numpy/core/src/multiarray/dragon4.c seems to be a license found nowhere
> > > else, so I would also add "AND UNKNOWN" to PYTHON3_NUMPY_LICENSE and
> add
> > > its verbatim license text with startline and endline parameters in
> > > PYTHON3_NUMPY_LICENSE_FILES. PTXdist extracts all those license
> > > texts mentioned in that variable and adds them to the license report,
> > > so it doesn't get lost too :)
>
On re-reading this: The license in dragon4.c is just MIT. So while it is OK
to add it to LICENSE_FILES I think we should not add the "AND unknown" bit.
I am sending v5, sorry for the noise.
Guillermo
[-- Attachment #1.2: Type: text/html, Size: 1163 bytes --]
[-- Attachment #2: Type: text/plain, Size: 92 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-11-14 10:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 15:13 [ptxdist] [PATCH] " Guillermo Rodríguez
2019-11-12 9:32 ` [ptxdist] [PATCH v2] " Guillermo Rodríguez
2019-11-12 9:51 ` [ptxdist] [PATCH] " Roland Hieber
2019-11-12 11:48 ` Guillermo Rodriguez Garcia
2019-11-12 11:51 ` [ptxdist] [PATCH v3] " Guillermo Rodríguez
2019-11-13 9:36 ` Roland Hieber
2019-11-14 9:36 ` Guillermo Rodriguez Garcia
2019-11-14 9:56 ` Roland Hieber
2019-11-14 10:01 ` Guillermo Rodriguez Garcia
2019-11-14 10:03 ` [ptxdist] [PATCH v4] " Guillermo Rodríguez
2019-11-14 10:07 ` Guillermo Rodriguez Garcia [this message]
2019-11-14 10:09 ` [ptxdist] [PATCH v5] " Guillermo Rodríguez
2019-11-14 20:24 ` Ladislav Michl
2019-11-14 11:18 ` [ptxdist] [PATCH v3] " Roland Hieber
2019-11-14 11:40 ` Guillermo Rodriguez Garcia
2019-11-14 13:31 ` Roland Hieber
2019-11-14 18:50 ` Guillermo Rodriguez Garcia
2019-11-15 8:51 ` [ptxdist] [PATCH v6] " Guillermo Rodríguez
2019-11-15 14:19 ` Michael Olbrich
2019-11-15 20:11 ` [ptxdist] [PATCH] " Guillermo Rodriguez Garcia
2019-11-19 9:10 ` Guillermo Rodriguez Garcia
2019-11-19 9:23 ` Michael Olbrich
2019-11-19 10:15 ` Guillermo Rodriguez Garcia
2019-11-19 12:39 ` [ptxdist] [PATCH v7] " Guillermo Rodríguez
2019-11-25 6:32 ` Michael Olbrich
2019-11-25 9:35 ` Guillermo Rodriguez Garcia
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='CABDcavZoyCCHh=Ubh15LnncCCU-P5MrBZr2PiiJPu-vXHH0zMA@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
--cc=rhi@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