public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Roman" <davidroman96@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: licenses/
Date: Mon, 18 Sep 2023 16:11:10 +0000 (UTC)	[thread overview]
Message-ID: <1695053424.bd661c15b0fe22de64b6426650f901f0e0d37bb8.davidroman@gentoo> (raw)

commit:     bd661c15b0fe22de64b6426650f901f0e0d37bb8
Author:     David Roman <davidroman96 <AT> gmail <DOT> com>
AuthorDate: Mon Sep 18 16:10:24 2023 +0000
Commit:     David Roman <davidroman96 <AT> gmail <DOT> com>
CommitDate: Mon Sep 18 16:10:24 2023 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=bd661c15

licenses: remove Baekmuk license, duplicate of BAEKMUK::gentoo

Signed-off-by: David Roman <davidroman96 <AT> gmail.com>

 licenses/Baekmuk | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/licenses/Baekmuk b/licenses/Baekmuk
deleted file mode 100644
index 04322ec737..0000000000
--- a/licenses/Baekmuk
+++ /dev/null
@@ -1,11 +0,0 @@
-Copyright (c) 1986-2002 Kim Jeong-Hwan
-All rights reserved.
-
-Permission to use, copy, modify and distribute this font is
-hereby granted, provided that both the copyright notice and
-this permission notice appear in all copies of the font,
-derivative works or modified versions, and that the following
-acknowledgement appear in supporting documentation:
-    Baekmuk Batang, Baekmuk Dotum, Baekmuk Gulim, and
-    Baekmuk Headline are registered trademarks owned by
-    Kim Jeong-Hwan.


             reply	other threads:[~2023-09-18 16:11 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 16:11 David Roman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-06  2:13 [gentoo-commits] repo/proj/guru:dev commit in: licenses/ 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-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=1695053424.bd661c15b0fe22de64b6426650f901f0e0d37bb8.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