From: Dirk Hohndel <dirk@hohndel.org>
To: Sean Paul <seanpaul@chromium.org>
Cc: "Thomas Hellstrom" <thellstrom@vmware.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] Add SPDX idenitifier and clarify license
Date: Thu, 3 May 2018 17:41:53 +0200 [thread overview]
Message-ID: <20180503154153.GF1309@rrmbpvm.gr8dns.org> (raw)
In-Reply-To: <20180503124620.GY73214@art_vandelay>
On Thu, May 03, 2018 at 08:46:20AM -0400, Sean Paul wrote:
>
> Thank you for the awesome summary, it is very helpful! So since the boilerplate
> has to stay, is there a benefit to adding the SPDX header? Is it just to make
> scripting/scraping easier?
Actually, the header now adds the correct information. Without the header
it is not clear that these files are supposed to be dual licensed under
MIT or GPL-2.
And yes, it of course simplifies tooling as well, which is why there is a
push to get these headers broadly added to many open source projects.
/D
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-03 15:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 13:46 [PATCH] Add SPDX idenitifier and clarify license Thomas Hellstrom
2018-05-02 14:00 ` Christian König
2018-05-02 14:41 ` Thomas Hellstrom
2018-05-02 14:56 ` Dirk Hohndel
2018-05-14 16:00 ` Alex Deucher
2018-05-14 16:06 ` Christian König
2018-05-02 20:12 ` Sean Paul
2018-05-02 20:33 ` Sean Paul
2018-05-02 21:25 ` Dirk Hohndel
2018-05-03 12:46 ` Sean Paul
2018-05-03 15:41 ` Dirk Hohndel [this message]
2018-05-08 21:52 ` Alex Deucher
2018-05-08 23:11 ` Dirk Hohndel
2018-05-09 5:25 ` Thomas Hellstrom
2018-05-04 14:36 ` Christian König
2018-05-03 13:03 ` Fabio Estevam
2018-05-03 13:12 ` Christian König
2018-05-03 15:48 ` Dirk Hohndel
2018-05-03 15:53 ` Fabio Estevam
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=20180503154153.GF1309@rrmbpvm.gr8dns.org \
--to=dirk@hohndel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=seanpaul@chromium.org \
--cc=thellstrom@vmware.com \
/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