summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobin H. Johnson <robbat2@gentoo.org>2015-08-08 13:49:04 -0700
committerRobin H. Johnson <robbat2@gentoo.org>2015-08-08 17:38:18 -0700
commit56bd759df1d0c750a065b8c845e93d5dfa6b549d (patch)
tree3f91093cdb475e565ae857f1c5a7fd339e2d781e /licenses/xref.lisp
downloadgentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.gz
gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.bz2
gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.zip
proj/gentoo: Initial commit
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed
Diffstat (limited to 'licenses/xref.lisp')
-rw-r--r--licenses/xref.lisp47
1 files changed, 47 insertions, 0 deletions
diff --git a/licenses/xref.lisp b/licenses/xref.lisp
new file mode 100644
index 000000000000..8dee00c635ce
--- /dev/null
+++ b/licenses/xref.lisp
@@ -0,0 +1,47 @@
+****************************************************************
+General License Agreement and Lack of Warranty *****************
+****************************************************************
+
+This software is distributed in the hope that it will be useful (both
+in and of itself and as an example of lisp programming), but WITHOUT
+ANY WARRANTY. The author(s) do not accept responsibility to anyone for
+the consequences of using it or for whether it serves any particular
+purpose or works at all. No warranty is made about the software or its
+performance.
+
+Use and copying of this software and the preparation of derivative
+works based on this software are permitted, so long as the following
+conditions are met:
+ o The copyright notice and this entire notice are included intact
+ and prominently carried on all copies and supporting documentation.
+ o No fees or compensation are charged for use, copies, or
+ access to this software. You may charge a nominal
+ distribution fee for the physical act of transferring a
+ copy, but you may not charge for the program itself.
+ o If you modify this software, you must cause the modified
+ file(s) to carry prominent notices (a Change Log)
+ describing the changes, who made the changes, and the date
+ of those changes.
+ o Any work distributed or published that in whole or in part
+ contains or is a derivative of this software or any part
+ thereof is subject to the terms of this agreement. The
+ aggregation of another unrelated program with this software
+ or its derivative on a volume of storage or distribution
+ medium does not bring the other program under the scope
+ of these terms.
+ o Permission is granted to manufacturers and distributors of
+ lisp compilers and interpreters to include this software
+ with their distribution.
+
+This software is made available AS IS, and is distributed without
+warranty of any kind, either expressed or implied.
+
+In no event will the author(s) or their institutions be liable to you
+for damages, including lost profits, lost monies, or other special,
+incidental or consequential damages arising out of or in connection
+with the use or inability to use (including but not limited to loss of
+data or data being rendered inaccurate or losses sustained by third
+parties or a failure of the program to operate as documented) the
+program, even if you have been advised of the possibility of such
+damanges, or for any claim by any other party, whether in an action of
+contract, negligence, or other tortious action.