diff options
| author | Edward Thomson <ethomson@edwardthomson.com> | 2023-02-22 22:44:03 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-22 22:44:03 +0000 |
| commit | 3ebe0741f7d41e4e9fcd64feca347f86ea8b70d7 (patch) | |
| tree | 9a3aa1d779b40825b22375d46897faa14d70e218 | |
| parent | 3b7137415b192da14a2203f25d66ef2b51f91463 (diff) | |
| download | libgit2-3ebe0741f7d41e4e9fcd64feca347f86ea8b70d7.tar.gz | |
Update README.md
Update based on carlosmn suggestions.
| -rw-r--r-- | README.md | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -25,11 +25,11 @@ and on Git hosting providers like [GitHub](https://github.com/), We perform the merge every time you click "merge pull request". `libgit2` is licensed under a **very permissive license** (GPLv2 with a special -Linking Exception). The GPLv2 requires you to make changes you make _to libgit2 -itself_ available publicly, but the linking exception means that you can link -libgit2 with your software without it becoming "infected" by the libgit2 -license. Additionally, the example code has been released to the public -domain (see the [separate license](examples/COPYING) for more information). +Linking Exception). This means that you can link against the library with any +kind of software without making that software fall under the GPL. +Changes to libgit2 would still be covered under its GPL license. +Additionally, the example code has been released to the public domain (see the +[separate license](examples/COPYING) for more information). Table of Contents ================= |