From: Jeff King <peff@peff.net>
To: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jonathan Smith <Jonathan.Smith@fphcare.co.nz>,
Junio C Hamano <gitster@pobox.com>,
Philip Oakley <philipoakley@iee.org>,
GitList <git@vger.kernel.org>
Subject: Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data
Date: Mon, 1 Feb 2016 03:16:50 -0500 [thread overview]
Message-ID: <20160201081650.GB26215@sigill.intra.peff.net> (raw)
In-Reply-To: <20160201081431.GA26215@sigill.intra.peff.net>
On Mon, Feb 01, 2016 at 03:14:31AM -0500, Jeff King wrote:
> On a more serious note, this FAQ (and the one right after) might be
> useful for convincing people:
>
> http://www.gnu.org/licenses/gpl-faq.en.html#GPLOutput
>
> Data that git stores is not strictly "output", but I think the answers
> there are relevant. And presumably written or vetted by lawyers, too.
Whoops, I just noticed this is the exact entry from Philip's patch. :-/
Sorry for the noise (and I do think it is a good link to help answer
this question, but I agree with Junio that we can let that FAQ stand on
its own without adding our own amateur-lawyer language to it).
-Peff
next prev parent reply other threads:[~2016-02-01 8:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 3:08 GPL v2 authoritative answer on stored code as a derived work Jonathan Smith
2016-01-25 19:06 ` Junio C Hamano
2016-01-27 23:58 ` Philip Oakley
2016-01-28 8:16 ` Johannes Schindelin
2016-01-31 20:51 ` Philip Oakley
2016-01-31 21:00 ` [RFC/PATCH] Git doc: GPL2 does not apply to repo data Philip Oakley
2016-01-31 22:08 ` Junio C Hamano
2016-01-31 22:15 ` Jonathan Smith
2016-02-01 7:35 ` Johannes Schindelin
2016-02-01 7:49 ` Matthieu Moy
2016-02-01 8:14 ` Jeff King
2016-02-01 8:16 ` Jeff King [this message]
2016-02-01 10:57 ` Philip Oakley
2016-02-01 10:53 ` Philip Oakley
2016-02-01 11:34 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160201081650.GB26215@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=Jonathan.Smith@fphcare.co.nz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=matthieu.moy@grenoble-inp.fr \
--cc=philipoakley@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).