From: Allison Randal <allison@lohutok.net>
To: Max Mehl <max.mehl@fsfe.org>
Cc: linux-spdx@vger.kernel.org
Subject: Re: Implement SPDX-Copyright
Date: Fri, 24 May 2019 11:13:09 -0400 [thread overview]
Message-ID: <ae737a9f-c8ce-a942-1ba7-9344768f6e12@lohutok.net> (raw)
In-Reply-To: <1558706708.m0wpla3nbm.2220@fsfe.org>
On 5/24/19 10:22 AM, Max Mehl wrote:
>
> Currently, the REUSE and SPDX team are discussing the official
> introduction of the *SPDX-Copyright* tag [^1] [^2], perhaps for SPDX 2.2
> and REUSE 3.0.
[...]
> What do you think? Would someone see issues with realising this
> technically rather simple change in the same course of action?
Since it is still under discussion, we should wait until that discussion
settles out before considering a massive application.
Allison
next prev parent reply other threads:[~2019-05-24 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 14:22 Implement SPDX-Copyright Max Mehl
2019-05-24 14:56 ` Greg KH
2019-05-24 15:13 ` Allison Randal [this message]
2019-05-24 17:19 ` Armijn Hemel - Tjaldur Software Governance Solutions
[not found] ` <EB311DAA-9909-462C-AE94-7513374683CB@jilayne.com>
2019-05-31 0:26 ` J Lovejoy
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=ae737a9f-c8ce-a942-1ba7-9344768f6e12@lohutok.net \
--to=allison@lohutok.net \
--cc=linux-spdx@vger.kernel.org \
--cc=max.mehl@fsfe.org \
/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;
as well as URLs for NNTP newsgroup(s).