linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Schrober <franzschrober@yahoo.de>,
	Linux-Sparse <linux-sparse@vger.kernel.org>
Cc: Christopher Li <sparse@chrisli.org>, Peter Anvin <hpa@zytor.com>,
	Dan Carpenter <error27@gmail.com>
Subject: Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
Date: Thu, 07 Nov 2013 08:18:40 -0800	[thread overview]
Message-ID: <527BBD60.3020503@infradead.org> (raw)
In-Reply-To: <1778650.2HXIBSXfmv@bentobox>

On 11/07/13 01:46, Schrober wrote:
> On Wednesday 06 November 2013 11:40:29 Christopher Li wrote:
>> On Wed, Nov 6, 2013 at 9:16 AM, H. Peter Anvin <hpa@zytor.com> wrote:
>>> I have a copy; I have uploaded it to:
>>>
>>> http://git.zytor.com/?p=users/hpa/sparse/sparse.git;a=commitdiff;h=23525c1
>>> 4bc263d70165fedf469d35cdb31b0ac35
>>>
>>> It would be good if someone would not only pull this but merge it into
>>> the master branch of the main sparse repo.
>>
>> Good idea. Let me do that.
> 
> Would be nice when you would do that or at least add a "relicense" branch to
> have it available for the relicensing process.
> 
> The following Authors may have to be asked for their aggreement to relicense
> their work under the MIT license. The data is gathered by checking the author
> field between
> 1bcc92138dcdf718dc3e0c694565f56e669d6ee3..1c1a74106ea78f624105be6a9bb5d24268f38d91
> (chrisl's sparse repo). At least I understood the idea behind this thread so [1].
>
> Randy Dunlap <randy.dunlap@oracle.com>

I agree to relicense under the MIT license.

thanks,
-- 
~Randy

  parent reply	other threads:[~2013-11-07 16:18 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
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 [this message]
     [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=527BBD60.3020503@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=error27@gmail.com \
    --cc=franzschrober@yahoo.de \
    --cc=hpa@zytor.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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).