linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Franz Schrober <franzschrober@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: jw+debian@jameswestby.net, sparse@chrisli.org, franzschrober@gmail.com
Subject: [PATCHv2 0/5] sparse: Relicense from non-dfsg-free OSL 1.1 to MIT license
Date: Thu, 28 Nov 2013 11:16:17 +0100	[thread overview]
Message-ID: <1385633782-775-1-git-send-email-franzschrober@gmail.com> (raw)

Hi,

many different people (especially Dan Carpenter) worked quite hard to contact
all people with significant contributions. The two changes are the ones which
should change the license from the problematic OSL[1] to the more liberal MIT
license. The initial agreement was reached when Novafora (successor in
interest to Transmeta Corporation) accepted such a license [2]. The commit
provided by them is attached as "relicense.bundle" [3] and has to be 
unbundled+merged in the sparse repository before the following patches can be
applied.

The changes can also be pulled from

        git pull https://github.com/franzschrober/sparse.git master

Btw. when somebody has to ask me in the future about a license change of these
two patches: do whatever you want. They can be considered public domain.

The change of this patchset compared to the first version are:

 * Benjamin Herrenschmidt and Chris Wedgwood were added to the Acked-by list
   because they've also agreed to the license change
 * Reverts for James Westby's contributions were added because it seems that he
   is the only person not agreeing to the license change (he was not reachable
   over social media or any of his email accounts)
 * An alternative patch for the implicit casting bug found James Westby was
   added

[1] https://wiki.debian.org/DFSGLicenses#Open_Software_License_.28OSL.29_v1.1
[2] http://lwn.net/Articles/328560/
[3] http://marc.info/?l=linux-sparse&m=138548610116314&w=2


             reply	other threads:[~2013-11-28 10:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 10:16 Franz Schrober [this message]
2013-11-28 10:16 ` [PATCHv2 1/5] Revert "Update the information in README about using the library." Franz Schrober
2013-11-28 10:16 ` [PATCHv2 2/5] Revert "Fix mistaken comparison that becomes a no-op." Franz Schrober
2013-11-28 10:16 ` [PATCHv2 3/5] sparse: Relicense under the MIT license Franz Schrober
2013-11-28 10:16 ` [PATCHv2 4/5] FAQ: Remove outdated section about the license Franz Schrober
2013-11-28 21:05   ` Josh Triplett
2013-11-29 12:19     ` Schrober
2013-11-29 12:30   ` [PATCHv3 4/5] FAQ: Remove outdated sections " Franz Schrober
2013-11-28 10:16 ` [PATCHv2 5/5] sparse: Also check bit_offset when checking implicit casts Franz Schrober
2013-11-28 10:22 ` [PATCHv2 0/5] sparse: Relicense from non-dfsg-free OSL 1.1 to MIT license Franz Schrober
     [not found] ` <CANeU7Qkjvh4OeCWANFbV6COU4NvjB1pUGXwry7CNCrQz8WG0zw@mail.gmail.com>
2013-11-29 23:18   ` Fwd: " Christopher Li
2013-11-30 12:48   ` Franz Schrober
2013-12-03  8:17 ` Franz Schrober
2013-12-03 10:37   ` Dan Carpenter
2013-12-03 11:02     ` Schrober

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=1385633782-775-1-git-send-email-franzschrober@gmail.com \
    --to=franzschrober@gmail.com \
    --cc=jw+debian@jameswestby.net \
    --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).