unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Brendan Tildesley <mail@brendan.scot>
Cc: 35449@debbugs.gnu.org
Subject: [bug#35449] [PATCH 1/7] gnu: zimg: Fix license field to refer to license:wtfpl2.
Date: Mon, 06 May 2019 10:33:36 +0200	[thread overview]
Message-ID: <87r29cm17j.fsf@gnu.org> (raw)
In-Reply-To: <20190427114307.26796-1-mail@brendan.scot> (Brendan Tildesley's message of "Sat, 27 Apr 2019 21:43:01 +1000")

Brendan Tildesley <mail@brendan.scot> skribis:

> -    (license (license:fsf-free "file://COPYING")))) ;WTFPL version 2
> +    (license (license:wtfpl2))))
                ^
I fixed this typo.  I also run ‘guix lint -c license’ to make sure
everything was OK.

  parent reply	other threads:[~2019-05-06  8:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e6b47bd1-b92d-598b-1b48-5a0eeacd51db@brendan.scot>
2019-04-27 11:43 ` [bug#35449] [PATCH 1/7] gnu: zimg: Fix license field to refer to license:wtfpl2 Brendan Tildesley
2019-04-27 11:43   ` [bug#35449] [PATCH 2/7] gnu: Use license: prefix in shellutils.scm Brendan Tildesley
2019-04-27 11:43   ` [bug#35449] [PATCH 3/7] gnu: envstore: Fix license field to refer to license:wtfpl2 Brendan Tildesley
2019-04-27 11:43   ` [bug#35449] [PATCH 4/7] gnu: python-pyyaml: " Brendan Tildesley
2019-04-27 11:43   ` [bug#35449] [PATCH 5/7] gnu: Use license: prefix in tmux.scm Brendan Tildesley
2019-04-27 11:43   ` [bug#35449] [PATCH 6/7] gnu: tmux-themepack: Fix license field to refer to license:wtfpl2 Brendan Tildesley
2019-04-27 11:43   ` [bug#35449] [PATCH 7/7] gnu: quickswitch-i3: Fix license field to use license:wtfpl2 Brendan Tildesley
2019-05-06  8:33   ` Ludovic Courtès [this message]
2019-05-06  8:25 ` bug#35449: Various WTFPL2 license field fixes Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r29cm17j.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35449@debbugs.gnu.org \
    --cc=mail@brendan.scot \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).