public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Martin Mokrejs" <mmokrejs@fold.natur.cuni.cz>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: licenses/
Date: Thu, 20 Apr 2017 17:25:49 +0000 (UTC)	[thread overview]
Message-ID: <1492709141.405413ad9c289f994da35200f380f226cc553ccc.mmokrejs@gentoo> (raw)

commit:     405413ad9c289f994da35200f380f226cc553ccc
Author:     Martin Mokrejš <mmokrejs <AT> fold <DOT> natur <DOT> cuni <DOT> cz>
AuthorDate: Thu Apr 20 17:25:41 2017 +0000
Commit:     Martin Mokrejs <mmokrejs <AT> fold <DOT> natur <DOT> cuni <DOT> cz>
CommitDate: Thu Apr 20 17:25:41 2017 +0000
URL:        https://gitweb.gentoo.org/proj/sci.git/commit/?id=405413ad

dev-python/pyvcf: add license file

 licenses/pyvcf | 46 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)

diff --git a/licenses/pyvcf b/licenses/pyvcf
new file mode 100644
index 000000000..f37927b3a
--- /dev/null
+++ b/licenses/pyvcf
@@ -0,0 +1,46 @@
+Copyright (c) 2011-2012, Population Genetics Technologies Ltd, All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+list of conditions and the following disclaimer.  
+
+2. Redistributions in binary form must reproduce the above copyright notice, this
+list of conditions and the following disclaimer in the documentation and/or
+other materials provided with the distribution.  
+
+3. Neither the name of the Population Genetics Technologies Ltd nor the names of
+its contributors may be used to endorse or promote products derived from this
+software without specific prior written permission.  
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+Copyright (c) 2011 John Dougherty
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS 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. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


             reply	other threads:[~2017-04-20 17:25 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 17:25 Martin Mokrejs [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-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=1492709141.405413ad9c289f994da35200f380f226cc553ccc.mmokrejs@gentoo \
    --to=mmokrejs@fold.natur.cuni.cz \
    --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