From: "Ludovic Courtès" <ludo@gnu.org>
To: Demis Balbach <db@minikn.xyz>
Cc: 59664-done@debbugs.gnu.org
Subject: bug#59664: [PATCH] gnu: Add tuxedo-keyboard.
Date: Mon, 05 Dec 2022 17:39:38 +0100 [thread overview]
Message-ID: <87y1rloldh.fsf@gnu.org> (raw)
In-Reply-To: <20221128221758.6760-1-db@minikn.xyz> (Demis Balbach's message of "Mon, 28 Nov 2022 23:17:58 +0100")
Demis Balbach <db@minikn.xyz> skribis:
> * gnu/packages/linux.scm (tuxedo-keyboard): New variable.
[...]
> + (license license:gpl3)))
Change it to ‘gpl3+’ because source file headers carry the “or any later
version” wording.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-12-05 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 22:17 [bug#59664] [PATCH] gnu: Add tuxedo-keyboard Demis Balbach
2022-12-05 16:39 ` Ludovic Courtès [this message]
[not found] ` <handler.59664.D59664.167025838919721.notifdone@debbugs.gnu.org>
2022-12-05 19:30 ` [bug#59664] closed (Re: bug#59664: [PATCH] gnu: Add tuxedo-keyboard.) Demis Balbach
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=87y1rloldh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59664-done@debbugs.gnu.org \
--cc=db@minikn.xyz \
/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).