From: Z572 <zhengjunjie@iscas.ac.cn>
To: 66202-done@debbugs.gnu.org
Cc: dev@jpoiret.xyz, ngraves@ngraves.fr, zimon.toutoune@gmail.com,
othacehe@gnu.org, ludo@gnu.org, me@tobias.gr, rekado@elephly.net,
guix@cbaines.net
Subject: bug#66202: [PATCH v2] guix: licenses: Add blue-oak1.0.0.
Date: Wed, 20 Nov 2024 18:10:43 +0800 [thread overview]
Message-ID: <87bjya43mk.fsf@iscas.ac.cn> (raw)
In-Reply-To: <874j6meizo.fsf@iscas.ac.cn> (Zheng Junjie's message of "Wed, 11 Sep 2024 15:40:11 +0800")
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Zheng Junjie <zhengjunjie@iscas.ac.cn> writes:
> Nicolas Graves via Guix-patches via <guix-patches@gnu.org> writes:
>
>> On 2023-09-26 10:20, Nicolas Graves via Guix-patches via wrote:
>>
>>> * guix/licenses.scm (blue-oak1.0.0): New variable.
>>> * guix/import/utils.scm (%spdx-license-identifiers): Add license blueoak1.0.0.
>>> ---
>>> guix/import/utils.scm | 1 +
>>> guix/licenses.scm | 6 ++++++
>>> 2 files changed, 7 insertions(+)
>>
>> Just a quick reminder ;)
>
> looks like BlueOak-1.0.0 is now OSI-approved? Maybe we can merge this patch?
>
> http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2024-January/005453.html
>
> https://spdx.org/licenses/BlueOak-1.0.0.html
pushed, and adjust messsage, use
"https://opensource.org/license/blue-oak-model-license" for comment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-11-20 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 21:16 [bug#66202] [PATCH 0/1] Add the Blue Oak Model License Nicolas Graves via Guix-patches via
2023-09-26 8:20 ` [bug#66202] [PATCH v2] guix: licenses: Add blue-oak1.0.0 Nicolas Graves via Guix-patches via
2023-12-15 9:12 ` Nicolas Graves via Guix-patches via
2024-09-11 7:40 ` Zheng Junjie
2024-11-20 10:10 ` Z572 [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=87bjya43mk.fsf@iscas.ac.cn \
--to=zhengjunjie@iscas.ac.cn \
--cc=66202-done@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix@cbaines.net \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=ngraves@ngraves.fr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.