linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-sparse@vger.kernel.org, Robert Bedichek <rbedichek@novafora.com>
Subject: Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
Date: Tue, 14 Apr 2009 17:06:15 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0904141701110.4132@localhost.localdomain> (raw)
In-Reply-To: <49E51310.3050005@zytor.com>



On Tue, 14 Apr 2009, H. Peter Anvin wrote:
> 
> Novafora has agreed to relicense the copyrights in sparse that were previously
> owned by Transmeta (i.e. the work Linus did before 2003-07-01) under the MIT
> license.
> 
> Git repository:
> 
> http://git.kernel.org/?p=devel/sparse/novafora/sparse.git;a=summary

That commit is also merged into my copy of sparse at

        http://git.kernel.org/?p=linux/kernel/git/torvalds/sparse.git;a=summary

but it's mixed in with some of my other local changes (warnings for weak 
functions being used in the same compilation unit - it triggers a bug in 
some gcc versions), so if you want just the relicensing it's probably 
better to pull the 'Novafora' branch from the repo Peter points to.

Now, to actually relicense all of git we need to get all other authors to 
agree, but I think we pretty much had that agreement already several years 
ago. I'm certainly personally ok with just going with the MIT license, but 
if people want something else, then obviously that license is compatible 
with a lot of other open-source licenses..

		Linus

  reply	other threads:[~2009-04-15  0:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 22:49 Novafora relicenses Transmeta sparse copyrights under the MIT license H. Peter Anvin
2009-04-15  0:06 ` Linus Torvalds [this message]
2009-04-15 12:25   ` Alexey Zaytsev
2009-04-16  5:32     ` David Given
2009-04-17 10:16     ` Christopher Li
2011-02-09 19:41       ` Dan Carpenter
2011-02-09 20:05         ` H. Peter Anvin
2011-02-09 20:06         ` H. Peter Anvin
2013-11-06 16:14 ` Schrober
2013-11-06 17:16   ` H. Peter Anvin
2013-11-06 19:40     ` Christopher Li
2013-11-07  9:46       ` Schrober
2013-11-07 10:01         ` Dan Carpenter
2013-11-07 11:04           ` Michael Stefaniuc
2013-11-07 16:18         ` Randy Dunlap
     [not found]         ` <20131107212415.GV26669@mwanda>
2013-11-08 16:13           ` Schrober
2013-11-08 16:21             ` Frederic Crozat
2013-11-08 16:35             ` Peter Jones
2013-11-08 17:13             ` Pekka Enberg
2013-11-08 17:27             ` Dan Carpenter
2013-11-14 23:33               ` Jan Pokorný
2013-11-08 18:00             ` Dan Carpenter
2013-11-09  8:23             ` Schrober
2013-11-09  8:27               ` Joe Perches
2013-11-09 19:42               ` Adam DiCarlo
     [not found]               ` <CANeU7QmPf-ELk7b1C5AZ6xU7Rns2-ZR9VYCdVG8FTHi43Kopig@mail.gmail.com>
2013-11-11  3:58                 ` Christopher Li

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=alpine.LFD.2.00.0904141701110.4132@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=rbedichek@novafora.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;
as well as URLs for NNTP newsgroup(s).