public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Leonardo Hernandez" <leohdz172@outlook.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: licenses/
Date: Fri,  9 Sep 2022 02:57:58 +0000 (UTC)	[thread overview]
Message-ID: <1662691924.0af8fac5e831d2f66a489f096c7ab0c59a570dda.leohdz172@gentoo> (raw)

commit:     0af8fac5e831d2f66a489f096c7ab0c59a570dda
Author:     Leonardo Hernández Hernández <leohdz172 <AT> outlook <DOT> com>
AuthorDate: Fri Sep  9 02:34:33 2022 +0000
Commit:     Leonardo Hernandez <leohdz172 <AT> outlook <DOT> com>
CommitDate: Fri Sep  9 02:52:04 2022 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=0af8fac5

licenses: add Unicode-DFS-2016

required by zoxide-0.8.3

Signed-off-by: Leonardo Hernández Hernández <leohdz172 <AT> outlook.com>

 licenses/Unicode-DFS-2016 | 46 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)

diff --git a/licenses/Unicode-DFS-2016 b/licenses/Unicode-DFS-2016
new file mode 100644
index 000000000..85d0d580d
--- /dev/null
+++ b/licenses/Unicode-DFS-2016
@@ -0,0 +1,46 @@
+UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE
+
+See Terms of Use <https://www.unicode.org/copyright.html>
+for definitions of Unicode Inc.’s Data Files and Software.
+
+NOTICE TO USER: Carefully read the following legal agreement.
+BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S
+DATA FILES ("DATA FILES"), AND/OR SOFTWARE ("SOFTWARE"),
+YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE
+TERMS AND CONDITIONS OF THIS AGREEMENT.
+IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE
+THE DATA FILES OR SOFTWARE.
+
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright © 1991-2022 Unicode, Inc. All rights reserved.
+Distributed under the Terms of Use in https://www.unicode.org/copyright.html.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Unicode data files and any associated documentation
+(the "Data Files") or Unicode software and any associated documentation
+(the "Software") to deal in the Data Files or Software
+without restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, and/or sell copies of
+the Data Files or Software, and to permit persons to whom the Data Files
+or Software are furnished to do so, provided that either
+(a) this copyright and permission notice appear with all copies
+of the Data Files or Software, or
+(b) this copyright and permission notice appear in associated
+Documentation.
+
+THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
+ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT OF THIRD PARTY RIGHTS.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
+NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
+DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
+DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+PERFORMANCE OF THE DATA FILES OR SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder
+shall not be used in advertising or otherwise to promote the sale,
+use or other dealings in these Data Files or Software without prior
+written authorization of the copyright holder.


             reply	other threads:[~2022-09-09  2:58 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  2:57 Leonardo Hernandez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-07 13:25 [gentoo-commits] repo/proj/guru:dev commit in: licenses/ 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-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=1662691924.0af8fac5e831d2f66a489f096c7ab0c59a570dda.leohdz172@gentoo \
    --to=leohdz172@outlook.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