From: Schrober <franzschrober@yahoo.de>
To: Josh Triplett <josh@joshtriplett.org>, linux-sparse@vger.kernel.org
Cc: jw+debian@jameswestby.net, sparse@chrisli.org
Subject: Re: [PATCHv2 4/5] FAQ: Remove outdated section about the license
Date: Fri, 29 Nov 2013 13:19:25 +0100 [thread overview]
Message-ID: <9559710.fHTLTMBSE0@bentobox> (raw)
In-Reply-To: <20131128210538.GA15555@leaf>
On Thursday 28 November 2013 13:05:38 Josh Triplett wrote:
> This previous section on "Why not GPL?" is now inaccurate as well; the
> last paragraph no longer applies, given the MIT license.
Yes, you are completely right. I've missed it because I've only searched for
references to the OSL 1.1
--
Franz Schrober
next prev parent reply other threads:[~2013-11-29 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 10:16 [PATCHv2 0/5] sparse: Relicense from non-dfsg-free OSL 1.1 to MIT license Franz Schrober
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 [this message]
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=9559710.fHTLTMBSE0@bentobox \
--to=franzschrober@yahoo.de \
--cc=josh@joshtriplett.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.