From: "David Roman" <davidroman96@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: licenses/
Date: Mon, 07 Jul 2025 08:57:06 +0000 (UTC) [thread overview]
Message-ID: <1751875514.b5b06a8aeebd35f1bcff6a1355419c3f9bab0dae.davidroman@gentoo> (raw)
Message-ID: <20250707085706.rNMKNgrX6MT_xsoR-xBpZO82syYhc8TM98yJw7QaC0E@z> (raw)
commit: b5b06a8aeebd35f1bcff6a1355419c3f9bab0dae
Author: David Roman <davidroman96 <AT> gmail <DOT> com>
AuthorDate: Mon Jul 7 08:04:52 2025 +0000
Commit: David Roman <davidroman96 <AT> gmail <DOT> com>
CommitDate: Mon Jul 7 08:05:14 2025 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=b5b06a8a
licenses: remove GPL-2+-with-font-exception, added to ::gentoo
Signed-off-by: David Roman <davidroman96 <AT> gmail.com>
licenses/GPL-2+-with-font-exception | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/licenses/GPL-2+-with-font-exception b/licenses/GPL-2+-with-font-exception
deleted file mode 100644
index 126453920a..0000000000
--- a/licenses/GPL-2+-with-font-exception
+++ /dev/null
@@ -1,12 +0,0 @@
-As a special exception, if you create a document which uses this font,
-and embed this font or unaltered portions of this font into the
-document, this font does not by itself cause the resulting document to
-be covered by the GNU General Public License. This exception does not
-however invalidate any other reasons why the document might be covered
-by the GNU General Public License. If you modify this font, you may
-extend this exception to your version of the font, but you are not
-obligated to do so. If you do not wish to do so, delete this exception
-statement from your version.
-
-GNU General Public License, version 2 or any later version.
-See GPL-2+ for the full text of these licenses.
\ No newline at end of file
next reply other threads:[~2025-07-07 8:57 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 8:05 David Roman [this message]
2025-07-07 8:57 ` [gentoo-commits] repo/proj/guru:master commit in: licenses/ David Roman
-- strict thread matches above, loose matches on Subject: below --
2025-08-24 23:51 [gentoo-commits] repo/proj/guru:dev " Tim Sviridov
2025-07-15 12:57 Takuya Wakazono
2025-07-12 14:11 Lucio Sauer
2025-07-10 22:16 Nguyen Dinh Dang Duong
2025-06-03 10:45 David Roman
2025-05-09 0:09 Nicolas PARLANT
2025-05-05 7:10 Takuya Wakazono
2025-03-15 1:00 Itai Ferber
2024-11-07 13:25 Sebastian Engel
2024-11-07 13:25 Sebastian Engel
2024-10-21 9:57 Gonçalo Negrier Duarte
2024-08-06 2:13 Lucio Sauer
2024-07-28 22:49 Ivan Lloro
2024-07-05 11:35 Andrew Ammerlaan
2024-05-15 12:37 Julien Roy
2024-05-08 1:57 Lucio Sauer
2024-04-14 7:33 Robert Greener
2024-04-01 20:38 Lucio Sauer
2023-09-18 16:11 David Roman
2023-08-12 16:21 David Roman
2023-04-16 9:19 Rahul Sandhu
2023-01-12 3:29 Tony Olagbaiye
2023-01-12 2:42 Tony Olagbaiye
2022-12-01 23:03 Adrian Schollmeyer
2022-11-10 14:18 Pascal Jäger
2022-10-25 18:23 Adrian Schollmeyer
2022-10-25 18:21 Adrian Schollmeyer
2022-10-03 17:01 David Roman
2022-09-12 14:21 [gentoo-commits] repo/proj/guru:master " Florian Schmaus
2022-09-12 14:19 ` [gentoo-commits] repo/proj/guru:dev " Florian Schmaus
2022-09-10 23:38 Patrick Taylor
2022-09-09 2:57 Leonardo Hernandez
2022-09-08 9:34 Andrew Ammerlaan
2022-07-02 20:47 Yuan Liao
2022-06-26 2:36 Alessandro Barbieri
2022-06-26 2:36 Alessandro Barbieri
2022-06-17 0:35 Alessandro Barbieri
2022-06-05 1:09 Alessandro Barbieri
2022-06-03 18:32 Alessandro Barbieri
2022-05-08 1:58 Alessandro Barbieri
2022-02-12 2:31 Leonardo Hernandez
2021-07-19 14:08 Michal Gasewicz
2021-05-28 10:28 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-05-28 10:28 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-12-15 18:42 Michal Gasewicz
2020-11-09 9:04 Theo Anderson
2020-09-25 16:09 Andrew Ammerlaan
2020-09-25 11:38 Andrew Ammerlaan
2020-09-24 20:42 Jesús P Rey
2020-07-29 11:31 Andrew Ammerlaan
2020-06-27 11:25 Alexey Sokolov
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=1751875514.b5b06a8aeebd35f1bcff6a1355419c3f9bab0dae.davidroman@gentoo \
--to=davidroman96@gmail.com \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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