From: Linus Torvalds <torvalds@osdl.org>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
Cc: Junio C Hamano <junkio@cox.net>,
Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org
Subject: Re: Junio's wishes [Was: Re: Approxidate licensing]
Date: Tue, 10 Oct 2006 15:12:04 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610101509460.3952@g5.osdl.org> (raw)
In-Reply-To: <200610102054.k9AKsQ2a004095@laptop13.inf.utfsm.cl>
On Tue, 10 Oct 2006, Horst H. von Brand wrote:
>
> There is a small practical problem with that: How would you find out I'm
> using a modified version of your code internally? Also, the "distribution"
> part of GPLv2 is a useful filter: Only such modifications that are
> worthwhile to distribute get back, not each and every corner I paint myself
> into while playing around.
Hey, I obviously agree that the GPLv2 is a good license, but at the same
time, I think too many people tend to think _just_ about legal issues.
Sometimes the wishes of an author should matter, regardless of whether
there is any law that forces you to do so. So I personally think a license
that says: "if you improve this, give out the improvements regardless of
whether you distribute things further or not" is a nice sentiment, and
should be honored, regardless of whether you can legally enforce any such
private tinkering or not.
Linus
next prev parent reply other threads:[~2006-10-10 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 17:39 Approxidate licensing Daniel Barkalow
2006-10-10 18:17 ` Linus Torvalds
[not found] ` <1073a5540610101128q3fb9f68fsf3a28fbda20927d1@mail.gmail.com>
2006-10-10 18:33 ` Edesio Costa e Silva
2006-10-10 19:23 ` Junio C Hamano
2006-10-10 20:54 ` Junio's wishes [Was: Re: Approxidate licensing] Horst H. von Brand
2006-10-10 22:12 ` Linus Torvalds [this message]
2006-10-11 7:55 ` Approxidate licensing Junio C Hamano
2006-10-11 7:57 ` David Woodhouse
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=Pine.LNX.4.64.0610101509460.3952@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=vonbrand@inf.utfsm.cl \
/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).