{"thread":{"id":"37209","subject":"Git and Openssl license","startedAt":"2014-07-25T02:46:55Z","lastAt":"2014-07-25T02:46:55Z","messageCount":1,"participants":["JiaQiang Xu"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"246675","messageId":"CAJoV8tWFKwHikeaK+Aypz+XHkoHa2BUFrvOokWJb=ZUi=zySjA@mail.gmail.com","threadId":"37209","inReplyTo":null,"subject":"Git and Openssl license","fromName":"JiaQiang Xu","fromEmail":"xjqkilling@gmail.com","sentAt":"2014-07-25T02:46:55Z","receivedAt":"2014-07-25T02:46:55Z","isPatch":false,"sender":{"key":"xjqkilling@gmail.com","avatar":null},"body":"Hi all,\n\nI'm a developer of Seafile (https://github.com/haiwen/seafile) project.\nWe borrowed some source code from the Git project and are going to\nlicense our code in GPLv2. But one concern is that GPLv2 is not compatible\nwith the Openssl license. It requires an exception.\nAs far as I can see, Git also links with Openssl library. But I can't find an\nexception in the license of Git.\nSo what I want to ask is that, is it safe for us to use Git's code and link with\nOpenssl library?\n\nThanks,\n- Johnathan\n"}]}