emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#44015: closed ([PATCH] Fix license name mismatches)


From: GNU bug Tracking System
Subject: bug#44015: closed ([PATCH] Fix license name mismatches)
Date: Sat, 17 Oct 2020 20:33:02 +0000

Your message dated Sat, 17 Oct 2020 22:32:22 +0200
with message-id <87pn5g4mqx.fsf@gnu.org>
and subject line Re: [bug#44015] [PATCH] Fix license name mismatches
has caused the debbugs.gnu.org bug report #44015,
regarding [PATCH] Fix license name mismatches
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
44015: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44015
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH] Fix license name mismatches Date: Thu, 15 Oct 2020 18:42:18 +0200
This patch fixes some license name mismatches between @file{guix/licenses.scm} and @file[guix/import/utils.scm} (spdx-string->license).

Additionally, it would be nice to standardize all the license names and, maybe, pull the data from [SPDX][1].

[1]: https://spdx.org/licenses

Attachment: 0001-guix-Fix-license-naming-mismatches.patch
Description: Binary data


--- End Message ---
--- Begin Message --- Subject: Re: [bug#44015] [PATCH] Fix license name mismatches Date: Sat, 17 Oct 2020 22:32:22 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Hi,

Helio Machado <0x2b3bfa0@gmail.com> skribis:

> From 8288a57468f817318f9f2faf382806d9ca40fdf3 Mon Sep 17 00:00:00 2001
> From: Helio Machado <0x2b3bfa0+git@googlemail.com>
> Date: Thu, 15 Oct 2020 18:32:59 +0200
> Subject: [PATCH] guix: Fix license naming mismatches
>
> * guix/licenses.scm:
> Add missing CUA-OPL-1.0 and a small notice
> pointing to guix/import/utils.scm.
>
> * guix/import/utils.scm (spdx-string->license):
> Rename licenses to fit the internal names and
> add a small notice pointing to guix/licenses.scm

I tweaked the commit log to more closely follow our conventions and
applied it.  Thanks!

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]