From: "Philip Oakley" <philipoakley@iee.org>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "GitList" <git@vger.kernel.org>,
"Jonathan Smith" <Jonathan.Smith@fphcare.co.nz>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data
Date: Mon, 1 Feb 2016 11:34:59 -0000 [thread overview]
Message-ID: <A6666A494CC341ACBC83F1CA1FE4B00C@PhilipOakley> (raw)
In-Reply-To: 82BCD59FE1254625963FF9A6CB98DC51@PhilipOakley
From: "Philip Oakley" <philipoakley@iee.org>
>>
>> We should leave the lawyering to real lawyers and we should not add
>> unnecessary work of interpreting our amateurish loose statement to
>> our laywers.
>
> Given Jonathan's question, and your earlier feedback, it did feel that a
> bit of clear blue water would be useful between Git (the DVCS), and /.git/
> (the repo contents), even if it were only to clarify the issues...
s/if it were/if the discussions were/
I was *not* meaning that 'it' meant a doc patch.
sorry for the lack of clarity there.
>
> --
> Philip
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-02-01 11:35 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
2016-02-01 10:57 ` Philip Oakley
2016-02-01 10:53 ` Philip Oakley
2016-02-01 11:34 ` Philip Oakley [this message]
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=A6666A494CC341ACBC83F1CA1FE4B00C@PhilipOakley \
--to=philipoakley@iee.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=Jonathan.Smith@fphcare.co.nz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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