From: "Aisha Tammy" <gentoo@aisha.cc>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: licenses/
Date: Wed, 30 Dec 2020 21:13:20 +0000 (UTC) [thread overview]
Message-ID: <1609362167.938ea5e19f0728f4bc2f9f9adaa49804c324ead1.epsilon-0@gentoo> (raw)
commit: 938ea5e19f0728f4bc2f9f9adaa49804c324ead1
Author: Aisha Tammy <gentoo <AT> aisha <DOT> cc>
AuthorDate: Wed Dec 30 21:02:25 2020 +0000
Commit: Aisha Tammy <gentoo <AT> aisha <DOT> cc>
CommitDate: Wed Dec 30 21:02:47 2020 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=938ea5e1
licenses/NVIDIA-gdk: no longer needed
Signed-off-by: Aisha Tammy <gentoo <AT> aisha.cc>
licenses/NVIDIA-gdk | 32 --------------------------------
1 file changed, 32 deletions(-)
diff --git a/licenses/NVIDIA-gdk b/licenses/NVIDIA-gdk
deleted file mode 100644
index 769c505a7..000000000
--- a/licenses/NVIDIA-gdk
+++ /dev/null
@@ -1,32 +0,0 @@
-Copyright 1993-2014 NVIDIA Corporation. All rights reserved.
-
-NOTICE TO USER:
-
-This source code is subject to NVIDIA ownership rights under U.S. and
-international Copyright laws. Users and possessors of this source code
-are hereby granted a nonexclusive, royalty-free license to use this code
-in individual and commercial software.
-
-NVIDIA MAKES NO REPRESENTATION ABOUT THE SUITABILITY OF THIS SOURCE
-CODE FOR ANY PURPOSE. IT IS PROVIDED "AS IS" WITHOUT EXPRESS OR
-IMPLIED WARRANTY OF ANY KIND. NVIDIA DISCLAIMS ALL WARRANTIES WITH
-REGARD TO THIS SOURCE CODE, INCLUDING ALL IMPLIED WARRANTIES OF
-MERCHANTABILITY, NONINFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.
-IN NO EVENT SHALL NVIDIA BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL,
-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 THIS SOURCE CODE.
-
-U.S. Government End Users. This source code is a "commercial item" as
-that term is defined at 48 C.F.R. 2.101 (OCT 1995), consisting of
-"commercial computer software" and "commercial computer software
-documentation" as such terms are used in 48 C.F.R. 12.212 (SEPT 1995)
-and is provided to the U.S. Government only as a commercial end item.
-Consistent with 48 C.F.R.12.212 and 48 C.F.R. 227.7202-1 through
-227.7202-4 (JUNE 1995), all U.S. Government End Users acquire the
-source code with only those rights set forth herein.
-
-Any use of this source code in individual and commercial software must
-include, in the user documentation and internal comments to the code,
-the above Disclaimer and U.S. Government End Users Notice.
next reply other threads:[~2020-12-30 21:13 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 21:13 Aisha Tammy [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-02 12:36 [gentoo-commits] proj/sci:master commit in: licenses/ Andrew Ammerlaan
2022-12-01 22:08 Andrew Ammerlaan
2022-12-01 21:58 Andrew Ammerlaan
2022-01-25 15:36 Andrew Ammerlaan
2022-01-23 13:06 Andrew Ammerlaan
2021-08-31 9:45 Andrew Ammerlaan
2021-07-03 10:32 Andrew Ammerlaan
2021-03-06 16:47 Andrew Ammerlaan
2021-02-25 14:59 Andrew Ammerlaan
2021-02-04 10:50 Andrew Ammerlaan
2021-01-30 15:23 Andrew Ammerlaan
2021-01-24 21:05 Andrew Ammerlaan
2021-01-19 17:02 Andrew Ammerlaan
2020-12-31 18:49 Aisha Tammy
2020-12-20 23:29 Aisha Tammy
2020-10-21 14:59 Horea Christian
2020-10-20 21:40 Horea Christian
2019-10-29 9:09 Alexey Shvetsov
2019-10-29 8:31 Alexey Shvetsov
2019-07-07 18:32 Martin Mokrejs
2019-03-25 9:40 Martin Mokrejs
2018-06-21 18:43 Justin Lecher
2018-04-21 14:14 Martin Mokrejs
2017-04-20 17:27 Martin Mokrejs
2017-04-20 17:25 Martin Mokrejs
2017-03-21 19:22 Justin Lecher
2016-11-28 20:53 Marius Brehler
2016-07-15 13:23 Martin Mokrejs
2016-05-30 8:52 Marius Brehler
2016-01-05 22:29 Martin Mokrejs
2016-01-05 22:28 Martin Mokrejs
2015-11-02 8:32 Marius Brehler
2015-09-21 19:05 Justin Lecher
2015-05-18 13:05 Justin Lecher
2015-05-12 11:18 Justin Lecher
2015-05-04 14:45 Justin Lecher
2015-05-04 14:02 Justin Lecher
2015-04-18 1:15 Martin Mokrejs
2015-03-14 8:21 Justin Lecher
2015-03-14 8:21 Justin Lecher
2015-02-26 1:50 Christoph Junghans
2015-02-10 14:37 Justin Lecher
2015-01-26 7:58 Justin Lecher
2015-01-18 2:16 Christoph Junghans
2015-01-15 6:53 Justin Lecher
2015-01-10 14:07 Justin Lecher
2015-01-10 11:44 Justin Lecher
2015-01-08 23:19 Martin Mokrejs
2015-01-07 21:40 Martin Mokrejs
2014-12-17 15:28 Justin Lecher
2014-09-28 11:30 Justin Lecher
2014-09-05 15:24 Jauhien Piatlicki
2014-09-02 16:50 Jauhien Piatlicki
2014-04-16 22:31 Sebastien Fabbro
2014-03-24 11:55 Martin Mokrejs
2014-01-21 19:38 Reinis Danne
2013-10-28 4:29 Guillaume Horel
2013-10-22 15:14 Christoph Junghans
2013-09-14 17:50 Christoph Junghans
2013-09-12 5:40 Sebastien Fabbro
2013-08-29 16:00 Martin Mokrejs
2013-08-12 21:27 Sebastien Fabbro
2013-07-09 22:44 Justin Bronder
2013-07-09 1:17 Justin Bronder
2013-06-12 22:02 Sebastien Fabbro
2012-09-20 12:39 Justin Lecher
2012-09-20 12:39 Justin Lecher
2012-06-08 12:51 Justin Lecher
2012-03-04 13:25 Justin Lecher
2012-02-02 13:00 Thomas Kahle
2012-01-20 9:14 Andrew Savchenko
2012-01-08 12:14 Martin Mokrejs
2011-10-31 13:11 Justin Lecher
2011-02-18 23:05 Martin Mokrejs
2011-02-18 23:03 Martin Mokrejs
2011-02-14 18:49 Martin Mokrejs
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=1609362167.938ea5e19f0728f4bc2f9f9adaa49804c324ead1.epsilon-0@gentoo \
--to=gentoo@aisha.cc \
--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