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

1 files changed, 21 insertions, 0 deletions

diff --git a/licenses/phrack b/licenses/phrack
new file mode 100644
index 000000000000..3f146fa1d8e7
--- /dev/null
+++ b/licenses/phrack
@@ -0,0 +1,21 @@
+Copynow Disclaimer Information
+ The contents of all material available on this Internet site are copyrighted by Phrack Inc. 
+unless otherwise indicated.
+ 
+ Permission is granted to quote or reproduce parts or a whole article as long as the reference to 
+http://www.phrack.org and adequate credit to the author is given (copynow).
+ 
+ All information in Phrack Magazine is, to the best of the ability of the editors and 
+contributors, truthful and accurate. When possible, all facts are checked, all code is compiled. 
+However, we are not omniscient (hell, we don't even get paid). It is entirely possible something 
+contained within this publication is incorrect in some way. If this is the case, please drop us 
+some email so that we can correct it in a future issue.
+ 
+ Also, keep in mind that Phrack Magazine accepts no responsibility for the entirely stupid (or 
+illegal) things people may do with the information contained herein. Phrack is a compendium of 
+knowledge, wisdom, wit, and sass. We neither advocate, condone nor participate in any sort of 
+illicit behavior. But we will sit back and watch.
+ 
+ Lastly, it bears mentioning that the opinions that may be expressed in the articles of Phrack 
+Magazine are intellectual property of their authors.
+ These opinions do not necessarily represent those of the Phrack Staff.