From: "Thomas Kahle" <tom111@gmx.de>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: licenses/
Date: Thu, 2 Feb 2012 13:00:38 +0000 (UTC) [thread overview]
Message-ID: <150ab31d8fd7c1ff7072c62de84db57347fc9c83.tom111@gentoo> (raw)
commit: 150ab31d8fd7c1ff7072c62de84db57347fc9c83
Author: Thomas Kahle <tomka <AT> gentoo <DOT> org>
AuthorDate: Thu Feb 2 11:00:36 2012 +0000
Commit: Thomas Kahle <tom111 <AT> gmx <DOT> de>
CommitDate: Thu Feb 2 11:00:36 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=150ab31d
Add kash licence
---
licenses/kash | 19 +++++++++++++++++++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/licenses/kash b/licenses/kash
new file mode 100644
index 0000000..8e4985a
--- /dev/null
+++ b/licenses/kash
@@ -0,0 +1,19 @@
+KASH can be copied and distributed freely for any non-commercial purpose.
+
+If you copy KASH for somebody else, you may ask this person to refund your expenses. This should cover cost of media, copying and shipping. You are not allowed to ask for more than this. In any case you must give a copy of this copyright notice along with the program.
+
+If you obtain KASH please send us a short notice to that effect, e.g., an e-mail message to the address kant@math.tu-berlin.de containing your full name and address. This allows us to keep track of the number of KASH users.
+
+If you publish a mathematical result that was partly obtained using KASH, please cite
+
+ M. Daberkow, C. Fieker, J. Klüners, M. Pohst, K. Roegner and K. Wildanger: KANT V4, in J. Symbolic Comp. 24 (1997), 267-283.
+
+Also we would appreciate it if you could inform us about such a paper.
+
+You are permitted to modify and redistribute KASH, but you are not allowed to restrict further redistribution. That is to say proprietary modifications will not be allowed. We want all versions of KASH to remain free. If you modify any part of KASH and redistribute it, you must supply a `README' document. This should specify what modifications you made in which files. We do not want to take credit or be blamed for your modifications.
+
+Of course we are interested in all of your modifications. In particular we would like to see bug-fixes, improvements and new functions. So again we would appreciate it if you would inform us about all modifications you make.
+
+KASH is distributed by us without any warranty, to the extent permitted by applicable state law. We distribute KASH *as is* without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
+
+The entire risk as to the quality and performance of the program is with you. Should KASH prove defective, you assume the cost of all necessary servicing, repair or correction. In no case unless required by applicable law will we, and/or any other party who may modify and redistribute KASH as permitted above, be liable to you for damages, including lost profits, lost monies or other special, incidental or consequential damages arising out of the use or inability to use KASH.
next reply other threads:[~2012-02-02 13:00 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 13:00 Thomas Kahle [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-30 21:13 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-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=150ab31d8fd7c1ff7072c62de84db57347fc9c83.tom111@gentoo \
--to=tom111@gmx.de \
--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