diff options
| author | Edward Thomson <ethomson@edwardthomson.com> | 2023-02-20 20:37:45 +0000 |
|---|---|---|
| committer | Edward Thomson <ethomson@edwardthomson.com> | 2023-02-20 20:37:45 +0000 |
| commit | 3b7137415b192da14a2203f25d66ef2b51f91463 (patch) | |
| tree | 12470fbc2ce34e85582929d645a4466d8fc3bb24 /README.md | |
| parent | 96e85df607863f94b55aba088c1395095b52bba7 (diff) | |
| download | libgit2-3b7137415b192da14a2203f25d66ef2b51f91463.tar.gz | |
README: clarify the linking exception
We say that you can link libgit2 "unmodified"... "without having to release
its source code". Clarify that you can modify libgit2 - but you must
release _its_ source code back - and you can link libgit2 without having
to release _your software's_ source code.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 9 |
1 files changed, 5 insertions, 4 deletions
@@ -25,10 +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). This basically means that you can link it (unmodified) -with any kind of software without having to release its source code. -Additionally, the example code has been released to the public domain (see the -[separate license](examples/COPYING) for more information). +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). Table of Contents ================= |