From: Stefan Beller <stefanbeller@gmail.com>
To: Dennis Kaarsemaker <dennis@kaarsemaker.net>, dwheeler@dwheeler.com
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file
Date: Sat, 21 Mar 2015 21:20:31 -0700 [thread overview]
Message-ID: <550E430F.9010308@gmail.com> (raw)
In-Reply-To: <1426969262.3756.1.camel@kaarsemaker.net>
On 21.03.2015 13:21, Dennis Kaarsemaker wrote:
> On za, 2015-03-21 at 14:06 -0400, David A. Wheeler wrote:
>> Warn cloners if there is no LICENSE* or COPYING* file that makes
>> the license clear. This is a useful warning, because if there is
>> no license somewhere, then local copyright laws (which forbid many uses)
>> and terms of service apply - and the cloner may not be expecting that.
>
> Please no, especially not without an option to switch this off. Git is
> not only used in open source settings, this would be highly annoying at
> $work, where no repo has (or needs) such a file.
>
To spin this further it would be interesting to have
a server advertisement during git clone which indicates
if this setting is recommended to be set.
Then hosting sites popular in the open source world such as
github could enable this feature, and the client may enable
this for the currently cloned repository (the user may have
a global setting set to suppress this message though).
At $work the default of not advertising checking for such a
feature would be set.
next prev parent reply other threads:[~2015-03-22 4:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 18:06 [PATCH] clone: Warn if clone lacks LICENSE or COPYING file David A. Wheeler
2015-03-21 20:21 ` Dennis Kaarsemaker
2015-03-22 4:20 ` Stefan Beller [this message]
2015-03-22 4:59 ` Junio C Hamano
2015-03-23 16:46 ` David A. Wheeler
2015-03-23 21:00 ` Ævar Arnfjörð Bjarmason
2015-03-22 17:56 ` Ævar Arnfjörð Bjarmason
2015-04-03 21:18 ` David A. Wheeler
2015-04-03 21:26 ` Junio C Hamano
2015-03-26 16:56 ` Kevin D
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=550E430F.9010308@gmail.com \
--to=stefanbeller@gmail.com \
--cc=dennis@kaarsemaker.net \
--cc=dwheeler@dwheeler.com \
--cc=git@vger.kernel.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).