From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: ptxdist@pengutronix.de, Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 1/6] glslang: version bump 11.7.1 -> 1.3.204.0
Date: Fri, 25 Feb 2022 09:42:06 +0100 [thread overview]
Message-ID: <YhiWXg2RTFCUZ9c4@pengutronix.de> (raw)
In-Reply-To: <aeba404940f754d4caf66e8fa8388b5bb4e2dcbc.camel@pengutronix.de>
On Thu, Feb 24, 2022 at 05:07:18PM +0100, Philipp Zabel wrote:
> On Do, 2022-02-24 at 16:54 +0100, Roland Hieber wrote:
> > I guess this was just the usual beginning-of-year copyright date
> > bump?
>
> Hm, no, they added the Khronos license used by the SPIRV/GLSL.ext.*.h
> headers [1] and the full GPL-3.0 license text [2].
That's why we have the md5 and why there should always be a comment about
what changed in the license files...
> [1] https://github.com/KhronosGroup/glslang/commit/5944f672a83cb81d4307ba41316c14a35c81c1b1
> [2] https://github.com/KhronosGroup/glslang/commit/d465ac12ddb207fbc805b0f9952297afbb69f8e4
>
> I missed [1], I suppose GLSLANG_LICENSE should now be:
>
> BSD-3-clause AND BSD-2-clause AND MIT AND Apple-MIT-License AND Apache-2.0 AND (GPL-3.0-or-later WITH Bison-exception-2.2) AND Khronos
>From the PTXdist documentation[1]:
"If no license identifier matches, or if anything is unclear about the
licensing situation, use the identifier custom"
I hate it when people modify a common license. It's basically a MIT license
but they had to add an extra paragraph that's not really about licensing
anyways :-/.
Michael
[1] https://www.ptxdist.org/doc/dev_licenses.html#distillation-into-license-identifiers
> regards
> Philipp
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2022-02-25 8:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 10:17 Philipp Zabel
2022-02-23 10:17 ` [ptxdist] [PATCH 2/6] shaderc: version bump v2021.3 -> v2022.1 Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-23 10:17 ` [ptxdist] [PATCH 3/6] spirv-tools: version bump 2021.4 -> 1.3.204.0, separate spirv-headers Philipp Zabel
2022-02-24 15:56 ` Roland Hieber
2022-02-24 16:14 ` Philipp Zabel
2022-02-25 8:27 ` Michael Olbrich
2022-02-23 10:17 ` [ptxdist] [PATCH 4/6] vulkan-loader: version bump 1.2.198.1 -> 1.3.204.0 Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-23 10:17 ` [ptxdist] [PATCH 5/6] vulkan-tools: version bump 1.2.198.0 " Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-23 10:17 ` [ptxdist] [PATCH 6/6] vulkan-validationlayers: " Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-24 15:54 ` [ptxdist] [PATCH 1/6] glslang: version bump 11.7.1 " Roland Hieber
2022-02-24 16:07 ` Philipp Zabel
2022-02-25 8:42 ` Michael Olbrich [this message]
2022-02-25 8:24 ` Michael Olbrich
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=YhiWXg2RTFCUZ9c4@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--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