├── note ├── swk1992.txt ├── lwzhang.txt ├── wjk.txt ├── my-github-id.txt ├── testpull ├── PretendDemo.txt ├── dupengtao.txt ├── mark442.txt ├── my-git-linxiaolong.txt ├── pangbo.txt ├── test_pull.txt ├── muyunlei@gmail.txt ├── test_pull_request_dee.txt ├── learn_git.txt ├── galaxybing-demo.txt ├── guoyalun.md ├── test_for_pull_request.txt ├── test.txt ├── LYJ_LYJ@126.com ├── lintaian-github-pullrequest-test.txt ├── oxbambooxo.txt ├── vinson0420@163.com.txt ├── fkdtz.txt ├── test-AngiWANG.txt ├── test_fork_pull.txt ├── codeplayer2org.txt ├── haokee.txt ├── seancy.txt ├── fl0wjacky.txt ├── niyeqing.txt ├── annging.txt ├── captainwong.txt ├── my-github-wk.txt ├── beiyi.txt ├── cassie_git.txt ├── Luodinonesheng@gmail.com ├── readme.txt ├── Rockyzsu_Git_Study ├── your-github-id.txt ├── git-tool.md ├── git_note.md ├── Git_Commands@pengloo53.md └── LICENSE /note: -------------------------------------------------------------------------------- 1 | 谢谢你的教程哈 ！ 2 | -------------------------------------------------------------------------------- /swk1992.txt: -------------------------------------------------------------------------------- 1 | swk1992 -------------------------------------------------------------------------------- /lwzhang.txt: -------------------------------------------------------------------------------- 1 | 非常棒的教程！非常感谢！ -------------------------------------------------------------------------------- /wjk.txt: -------------------------------------------------------------------------------- 1 | hello world 2 | -------------------------------------------------------------------------------- /my-github-id.txt: -------------------------------------------------------------------------------- 1 | test pull 2 | -------------------------------------------------------------------------------- /testpull: -------------------------------------------------------------------------------- 1 | what is this for ? 2 | -------------------------------------------------------------------------------- /PretendDemo.txt: -------------------------------------------------------------------------------- 1 | thanks your guide! 2 | -------------------------------------------------------------------------------- /dupengtao.txt: -------------------------------------------------------------------------------- 1 | thanks for your guide! -------------------------------------------------------------------------------- /mark442.txt: -------------------------------------------------------------------------------- 1 | git教程非常详细,对于初学者非常有益,感谢分享. -------------------------------------------------------------------------------- /my-git-linxiaolong.txt: -------------------------------------------------------------------------------- 1 | import os 2 | -------------------------------------------------------------------------------- /pangbo.txt: -------------------------------------------------------------------------------- 1 | 感谢廖雪峰，只用3个小时就让我学会了git，非常棒的教程！ -------------------------------------------------------------------------------- /test_pull.txt: -------------------------------------------------------------------------------- 1 | this line has no contents. 2 | test -------------------------------------------------------------------------------- /muyunlei@gmail.txt: -------------------------------------------------------------------------------- 1 | 谢谢带来这么通俗易懂的Git教程！ 2 | Thx so much! 3 | -------------------------------------------------------------------------------- /test_pull_request_dee.txt: -------------------------------------------------------------------------------- 1 | 这个git系列教程真的做得十分不错.深入浅出.谢谢博主. 2 | -------------------------------------------------------------------------------- /learn_git.txt: -------------------------------------------------------------------------------- 1 | this is a request pull 2 | 3 | on GITHUB 4 | -------------------------------------------------------------------------------- /galaxybing-demo.txt: -------------------------------------------------------------------------------- 1 | 本地化版本控制 文件补丁 2 | Subversion 文件快照 3 | Git 镜像 -------------------------------------------------------------------------------- /guoyalun.md: -------------------------------------------------------------------------------- 1 | 感谢给我们贡献了如此浅显易懂的git教程。 2 | 真正的感觉自己git 可以轻松入门了！ 3 | 4 | -------------------------------------------------------------------------------- /test_for_pull_request.txt: -------------------------------------------------------------------------------- 1 | 在这里尝试下贡献代码。 2 | 谢谢你的文章，让我知道怎么使用git。 3 | -------------------------------------------------------------------------------- /test.txt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Rockyzsu/learngit/master/test.txt -------------------------------------------------------------------------------- /LYJ_LYJ@126.com: -------------------------------------------------------------------------------- 1 | 看了作者的博客，终于感觉对git有了一些基础理解了，作者提供了这么详细易懂的基础教程，小白再次表示深深的谢意。 2 | -------------------------------------------------------------------------------- /lintaian-github-pullrequest-test.txt: -------------------------------------------------------------------------------- 1 | hehe,pass or not pass,I don`t care! 2 | -------------------------------------------------------------------------------- /oxbambooxo.txt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Rockyzsu/learngit/master/oxbambooxo.txt -------------------------------------------------------------------------------- /vinson0420@163.com.txt: -------------------------------------------------------------------------------- 1 | Thank you for giving so good a session. 2 | I like it! 3 | -------------------------------------------------------------------------------- /fkdtz.txt: -------------------------------------------------------------------------------- 1 | my github-id is fkdtz,my name is lisong,my email is 2 | 595375808@qq.com 3 | -------------------------------------------------------------------------------- /test-AngiWANG.txt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Rockyzsu/learngit/master/test-AngiWANG.txt -------------------------------------------------------------------------------- /test_fork_pull.txt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Rockyzsu/learngit/master/test_fork_pull.txt -------------------------------------------------------------------------------- /codeplayer2org.txt: -------------------------------------------------------------------------------- 1 | 作者写的这本git教程生动有趣，相比其他的git教程，如git magic、pro git等容易理解的多，能够快速上手并在项目中实际使用。谢谢。 2 | -------------------------------------------------------------------------------- /haokee.txt: -------------------------------------------------------------------------------- 1 | 我倒是觉得git的学习起点是比较高的，但是按照作者的网页一点点敲，相信会有意想不到的收获，顶作者还有他的主页 http://www.liaoxuefeng.com。做的很棒，加油！！！ 2 | -------------------------------------------------------------------------------- /seancy.txt: -------------------------------------------------------------------------------- 1 | 2 | 这是我第二次学习廖雪峰老师的教程，此教程以通俗易懂的方式，从实用角度介绍了git的常用命令，如果你能通读这篇教程，使用git与人合作开发应该不成问题。推荐学习 3 | 4 | -------------------------------------------------------------------------------- /fl0wjacky.txt: -------------------------------------------------------------------------------- 1 | hello,Michael Liao. 2 | I teach myself programming from 3 years ago. 3 | Thank for your jobs. 4 | -------------------------------------------------------------------------------- /niyeqing.txt: -------------------------------------------------------------------------------- 1 | 作为一个纯自学者，PRO GIT虽好，但容易看晕，而且缺少实践。很感谢廖雪峰的这个教程，step by step，踏实而又不枯燥。好教程，赞一个！ 前面确实是用Notepad++ UTF8打开，误选了应用于打开ANSI文件所致。 2 | -------------------------------------------------------------------------------- /annging.txt: -------------------------------------------------------------------------------- 1 | I feel so sorry that I can't wirte this in Chinese and My English is pool. 2 | 3 | I write this for test the function of "pull reqest" -------------------------------------------------------------------------------- /captainwong.txt: -------------------------------------------------------------------------------- 1 | Thx for you contribution! 2 | I'm a fresh bird on git, thx your outstanding articles for helping me learn git. 3 | Respects 4 | captainwong -------------------------------------------------------------------------------- /my-github-wk.txt: -------------------------------------------------------------------------------- 1 | thank you, a good session 2 | 赞一个，非常好的教程！ 3 | 能否增加一些关于GIT挂钩的教程以及merge和rebase区别，谢谢! 4 | 5 | 老师有没有解决乱码的好方法呢，谢谢！windows下面，不知道如何解决，谢谢！ 6 | 7 | -------------------------------------------------------------------------------- /beiyi.txt: -------------------------------------------------------------------------------- 1 | 感谢廖雪峰给我们贡献了如此浅显易懂的git教程。 2 | 我不是一名程序员，但靠带领别人认识程序世界为职业。 3 | 我希望将来能通过这里所学的知识，把自己的一些学习体会和代码放在github上和大家分享。 4 | 5 | 如果说我对git的学习心得，那就是我把git看作vmware虚拟机快照管理器一样的东西。只不过做快照的对象是文本内容。 -------------------------------------------------------------------------------- /cassie_git.txt: -------------------------------------------------------------------------------- 1 | This is my first learn to pull request git. 2 | I love reading your git course. 3 | I find learning git is so interesting. 4 | I hope you could allow my pull request 5 | -------------------------------------------------------------------------------- /Luodinonesheng@gmail.com: -------------------------------------------------------------------------------- 1 | i'm learning the git! git is very cool and strong!i like it!and i really want test how to pull request,so ,i hope teacher liao that you can take this file!thank you ! 2 | -------------------------------------------------------------------------------- /readme.txt: -------------------------------------------------------------------------------- 1 | Git is a distributed version control system. 2 | Git is a free software distributed under the GPL. 3 | Git has a mutable index called stage. 4 | Git tracks changes of files. 5 | Creating a new branch is quick and simple. 6 | Git can merge branches. 7 | "test pull request." 8 | update by wk 9 | -------------------------------------------------------------------------------- /Rockyzsu_Git_Study: -------------------------------------------------------------------------------- 1 | Hi I am Rocky, now working at NVIDIA, as SWQA. 2 | This blog is very useful for me to learn git one step by step and build up my git repository in github. I need to send my great appriciation to YOU ! 3 | Now i am going to forward this blog to my friends , big alias to learn this course. 4 | 5 | Best regards, 6 | Rocky Chen 7 | -------------------------------------------------------------------------------- /your-github-id.txt: -------------------------------------------------------------------------------- 1 | 一口气全部看完了，讲得很详细很有黑皮书的感觉。硬是要说缺点的话就是github的多人合作介绍得不够具体。 2 | 我对github上的协作是这样理解的：fork就好比转载别人的文章，因为不转载是没有权限修改的。而转载后在自己的地盘想怎样就怎样。然后要把别人的文章下载到自己电脑上修改，这个就是clone。在自己电脑上修改完成后保存就是git add和git commit。想要发表到网上就是git push。发表了想让作者添加你的修改就得向作者提交请求，让作者知道你改了什么，这个就是pull request 3 | //工作区，缓存区，仓库和github这些还没想到比较好的比喻 4 | //用了your-github-id.txt这个文件名一定会被拒绝吧= = 5 | -------------------------------------------------------------------------------- /git-tool.md: -------------------------------------------------------------------------------- 1 | ## 推荐几款chrome上的github插件 2 | ---------- 3 | 4 | - [Octotree](https://github.com/buunguyen/octotree)：Browser extensions to display GitHub code in tree format. 5 | - [GistBox](https://chrome.google.com/webstore/detail/gistbox-desktop/pdjgfbgklbmmigkmmdbbhfchdldngkml) :GistBox is the best interface to Github Gists. Organize your snippets with labels. Edit your code. Search by description. All in one speedy app. 6 | - [GistBox Clipper](https://chrome.google.com/webstore/detail/gistbox-clipper/cejmhmbmafamjegaebkjhnckhepgmido)：GistBox Clipper is the companion extension to GistBox, the most beautiful way to organize code snippets. It allows a user to create a GitHub Gist from any page on the web. 7 | -------------------------------------------------------------------------------- /git_note.md: -------------------------------------------------------------------------------- 1 | # Git与GitHub 2 | 3 | 标签（空格分隔）： ReadingNote 4 | 5 | [toc] 6 | 7 | ----------------------- 8 | ## 常用命令 9 | - 开始时，克隆 10 | ``` 11 | $ git clone git@github.com:yourname/resp.git # 仅master 12 | $ git checkout -b dev origin/dev # 新建并克隆分支 13 | ``` 14 | - 查看状态 15 | ``` 16 | $ git status 17 | $ git diff #add之前 18 | $ git log [--pretty=oneline] 19 | $ git log -p -1 # 查看最近一次提交的修改 20 | $ git reflog # 查看使用过的命令 21 | ``` 22 | - 完成后，add与commit 23 | ``` 24 | $ git add . 25 | $ git commit -m "It's the comment." 26 | ``` 27 | - 版本回退 28 | ``` 29 | $ git reset --hard HEAD^^ # 回退两个版本 30 | $ git reset --hard HEAD~100 # 回退100个版本 31 | ``` 32 | - 撤销修改 33 | ``` 34 | $ git checkout -- # 撤销工作区中的修改 35 | $ git reset HEAD # 撤销add 36 | ``` 37 | - 添加标签（release） 38 | ``` 39 | $ git tag v0.1 [0f50c4] #为[0f50c4]设置标签v0.1 40 | $ git tag # 查看已有标签 41 | $ git show v0.1 # 查看v0.1 42 | $ git push origin --tags # 推送所有标签 43 | $ git tag -d v0.1 # 删除标签 44 | ``` 45 | -------------------------- 46 | ## 分支管理 47 | > git的分支管理，是文件指针的变化；git鼓励使用分支 48 | 49 | ### 基本操作 50 | - 创建分支 51 | ``` 52 | $ git checkout -b dev # 创建分支dev 53 | ``` 54 | - 切换分支 55 | ``` 56 | $ git checkout dev # 切换到dev 57 | ``` 58 | - 查看分支 59 | ``` 60 | $ git branch 61 | ``` 62 | - 合并分支 63 | ``` 64 | $ git merge [--no-ff -m "merge with no-ff"] dev 65 | ``` 66 | - 删除分支 67 | ``` 68 | $ git branch -d dev 69 | ``` 70 | - 保存现场 71 | ``` 72 | $ git stash 73 | $ git stash pop 74 | ``` 75 | ### 解决冲突 76 | - 有冲突时，无法合并，需要手工解决冲突 77 | - 通过`git status`查看冲突的文件 78 | - 打开冲突的文件，git已经标记了冲突的位置 79 | 80 | ###多人协作 81 | > 出现冲突时，先pull到本地，合并后再push 82 | 83 | - 远程提交 84 | ``` 85 | $ git push [-u] origin master # 第一次使用需要[-u] 86 | ``` 87 | - 建立关联 88 | ``` 89 | $ git branch --set-upstream dev origin/dev 90 | ``` 91 | - 本地同步 92 | ``` 93 | $ git pull 94 | ``` 95 | -------------------------- 96 | ## 第一次使用的基本配置 97 | - 产生`密钥` 98 | ``` 99 | $ ssh-keygen -t rsa -C "your_email@youremail.com" 100 | ``` 101 | - 在github中注册`公钥`（`~/.ssh/id_rsa.pub`） 102 | - 设置`username`与`email` 103 | ``` 104 | $ git config --global user.name "Your Name" 105 | $ git config --global user.email "email@example.com" 106 | ``` 107 | ----------------------- 108 | ## 参考资料 109 | 1. [廖雪峰的官方网站 - Git教程](http://www.liaoxuefeng.com/wiki/0013739516305929606dd18361248578c67b8067c8c017b000) 110 | 1. [Wuyuan's Blog](http://wuyuans.com/2012/05/github-simple-tutorial/) 111 | 1. [快乐&&平凡 - CSDN.NET](http://blog.csdn.net/wh_19910525/article/details/8128916) 112 | -------------------------------------------------------------------------------- /Git_Commands@pengloo53.md: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | layout: post 4 | title: "Git 常用命令" 5 | 6 | --- 7 | ###学会这些命令，你就可以熟练的使用Git工具了，什么？想精通，那是不可能的。 8 | ####基本上，Git就是以下面的命令顺序学习的。文中笔记是从廖雪峰老师的[Git教程](http://www.liaoxuefeng.com/wiki/0013739516305929606dd18361248578c67b8067c8c017b000)中总结出来的，方面查阅命令。详细原理请看[Git教程](http://www.liaoxuefeng.com/wiki/0013739516305929606dd18361248578c67b8067c8c017b000) 9 | ####1、基础 10 | - `git config --global user.name "Your Name"`设置你的仓库用户名（用于标识提交者） 11 | - `git config --global user.email "email@example.com"`设置你的仓库邮箱（用于标识提交者） 12 | - `git init` 初始化一个git仓库 13 | - `git add --all` 添加所有更改的文件 14 | - `git add filename1` 当然可以指定添加filename1 15 | - `git commit -m "commit message"` 添加更改的信息，必须要有，不然报错，不建议不加。 16 | - `git status` 查看git当前状态 17 | - `git diff filename1` 查看filename1到底修改了哪些内容 18 | - `git log` 查看最近的提交日志 19 | - `git log --pretty=oneline` 单行显示提交日志 20 | - `git reset --hard commitID` 利用`git log`得到的commitID返回版本 21 | - `git reset --hard HEAD^`回到上一个版本 22 | - `git reflog` 查看命令的历史，可以找到`git log`看不到的commitID，因为`git log`只显示当前的提交日志，如果你提交了一次，退回版本后又后悔了，就能查看上次提交的commitID 23 | - `git checkout -- filename1` 利用版本库中的版本替换工作区中的文件。功能有2： 24 | - 撤销文件修改，分两种情况： 25 | - 撤销工作区中的修改（没有使用`git add`命令添加到暂存区） 26 | - 撤销暂存区中的修改（添加到了暂存区又做了修改） 27 | - 找回删除的文件 28 | - 工作区中文件误删了，可以通过此命令从版本库中找回 29 | - `git reset HEAD filename1` 撤销add，回到工作区 30 | - `git rm filename1` 删除文件 31 | - `git remote add origin https://github.com/pengloo53/learngit.git` 将本地库关联到github远程库上 32 | - `git push -u origin master` 第一次推送的时候要加上`-u`参数，可以将本地库的master分支与远程库的master分支关联起来；下次提交就不需要加`-u`了。 33 | - `git clone https://github.com/pengloo53/learngit.git` 克隆远程库到本地 34 | 35 | ####2、分支管理 36 | - `git checkout -b dev`创建dev分支并切换到dev。相当于`git branch dev`、`git checkout dev`两条命令。 37 | - `git branch`查看当前分支 38 | - `git merge dev`合并指定分支到当前分支，如，你现在master分支，那么执行命令就将dev分支合并到了master分支上。 39 | - `git branch -d dev`删除dev分支 40 | - `git log --graph --pretty=oneline --abbrev-commit`查看分支合并图 41 | - `git merge --no-ff -m "merge with no-ff" dev`禁用「Fast forward」，也就是保留分支的相关信息。 42 | - `git stash` 将工作区现场储藏起来，等以后恢复后继续工作。通常用于处理更为着急的任务时，例如：bug。 43 | - `git stash list` 查看保存的工作现场 44 | - `git stash apply`恢复工作现场 45 | - `git stash drop` 删除stash内容 46 | - `git stash pop` 恢复的同时直接删除stash内容 47 | - `git stash apply stash@{0}` 恢复指定的工作现场，当你保存了不只一份工作现场时。 48 | - `git branch -D feature-vulcan` 强行删除分支。用于不需要合并，就地删除的情况。 49 | - `git remote` 查看远程库的信息，一般返回origin。 50 | - `git remote -v` 查看远程库的详细信息。 51 | - `git push origin master` 将本地master分支推送到远程master分支。 52 | - master分支为主分支，因此要时刻与远程同步； 53 | - dev分支为开发分支，团队成员都需要在上面工作，所以也需要与远程同步； 54 | - bug分支只用于在本地修复bug，没有必要推送到远程； 55 | - feature新功能分支是否推送到远程，取决于你是否和其他人合作在上面开发。 56 | - `git clone https://github.com/pengloo53/learngit.git` 将远程库克隆到本地，默认只能看到master分支。 57 | - `git checkout -b dev origin/dev` 创建远程dev分支到本地 58 | - `git pull` 将远程分支的最新内容抓取下来。 59 | - `git branch --set-upstream dev origin/dev`将本地dev分支与远程dev分支之间建立链接。 60 | 61 | #####_多人协作工作模式_ 62 | 1. 首先，可以试图用`git push origin branch-name`推送自己的修改； 63 | 2. 如果推送失败，则因为远程分支比你的本地更新，需要先用git pull试图合并（如果git pull提示“no tracking information”，则说明本地分支和远程分支的链接关系没有创建，用命令`git branch --set-upstream branch-name origin/branch-name`）; 64 | 3. 如果合并有冲突，则解决冲突，并在本地提交； 65 | 4. 没有冲突或者解决掉冲突后，再用`git push origin branch-name`推送就能成功！ 66 | 67 | ####3、标签管理 68 | - `git tag v1.0` 给当前分支打上标签 69 | - `git tag` 查看所有的标签，按时间顺序列出。 70 | - `git log --pretty=oneline --abbrev-commit`缩略commitID并单行显示提交信息 71 | - `git tag v0.9 commitID`通过上一条命令查看commitID，然后打上标签。用于忘记打标签的情况，因为标签其实就是只想某个commitID的指针，默认情况下，标签打在最新的提交上。 72 | - `git show v0.9` 查看标签信息。 73 | - `git tag -a v0.1 -m "version 0.1 released" commitID`创建带有说明的标签，`-a`指定标签名，`-m`指定说明文字。 74 | - `git tag -d v0.1` 删除标签v0.1 75 | - `git push origin v1.0` 推送标签1.0到远程 76 | - `git push origin --tags` 推送所有的标签到远程 77 | - `git push origin :refs/tags/v0.9` 删除远程标签，但是前提是要先在本地删除对应标签。 78 | 79 | ####4、自定义GitHub 80 | - `git config --global color.ui true` 让Git显示颜色 81 | - `.gitignore`在这个文件里编辑你要忽略的文件，并提交到Git中，就可以忽略特殊文件的检查。如将`*.db`写入`.gitignore`文件中，将忽略所有db文件。可以参考[github收集的所有.gitignore](https://github.com/github/gitignore) 82 | - `git config --global alias.st status`将status的别名设置成st，那么`git st`=`git status`。 83 | - `git config --global alias.unstage 'reset HEAD'` 那么`git reset HEAD filename`=`git unstage filename` 84 | - `git config --global alias.last 'log -1'` 敲`git last`就显示最后一次提交了。 85 | 86 | ####5、搭建Git服务器 87 | 1. `sudo apt-get install git` 安装Git； 88 | 2. `sudo adduser git` 添加Git用户； 89 | 3. `sudo git init --bare sample.git` 初始化git仓库； 90 | 4. `sudo chown -R git:git sample.git`修改仓库的所属用户为git； 91 | 5. 将git用户的信息`git:x:1001:1001:,,,:/home/git:/bin/bash`改成`git:x:1001:1001:,,,:/home/git:/bin/git-shell`，为了禁用shell登录。 92 | 6. `git clone git@server:/director/sample.git` 克隆Git服务器上的仓库 93 | 94 | _PS. 想方便管理公钥，用[Gitosis](https://github.com/res0nat0r/gitosis)；想控制权限，用[Gitolite](https://github.com/sitaramc/gitolite)。_ 95 | 96 | 97 | 98 | 99 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | --------------------------------------------------------------------------------