linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Franz Schrober <franzschrober@yahoo.de>
To: linux-sparse@vger.kernel.org
Cc: sparse@chrisli.org, Franz Schrober <franzschrober@yahoo.de>
Subject: [PATCH 2/2] FAQ: Remove outdated section about the license
Date: Tue, 26 Nov 2013 18:11:15 +0100	[thread overview]
Message-ID: <1385485875-4379-2-git-send-email-franzschrober@yahoo.de> (raw)
In-Reply-To: <1385485875-4379-1-git-send-email-franzschrober@yahoo.de>

Signed-off-by: Franz Schrober <franzschrober@yahoo.de>
---
 FAQ | 17 -----------------
 1 file changed, 17 deletions(-)

diff --git a/FAQ b/FAQ
index 290de0e..56a2618 100644
--- a/FAQ
+++ b/FAQ
@@ -50,23 +50,6 @@ A.  See the previous question: I personally think that the front end
     improvements back. That's your "quid" to my "quo".
 
 
-Q.  So what _is_ the license?
-
-A.  I don't know yet.  I originally thought it would be LGPL, but I'm
-    possibly going for a license that is _not_ subsumable by the GPL. 
-    In other words, I don't want to see a GPL'd project suck in the
-    LGPL'd front-end, and then make changes to the front end under the
-    GPL (this is something that the LGPL expressly allows, and see the
-    previous question for why I think it's the _only_ thing that I will
-    not allow). 
-
-    The current front-runner is the OSL ("Open Software License", see
-    http://www.opensource.org/licenses/osl.php), together with a note on
-    what makes source derivative and what does not to make it clear that
-    people can write back-ends for it without having to make those
-    back-ends available under the OSL. 
-

      reply	other threads:[~2013-11-26 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 17:09 [PATCH 0/2] sparse: Relicense from non-dfsg-free OSL 1.1 to MIT license Schrober
2013-11-26 17:11 ` [PATCH 1/2] sparse: Relicense under the " Franz Schrober
2013-11-26 17:11   ` Franz Schrober [this message]

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=1385485875-4379-2-git-send-email-franzschrober@yahoo.de \
    --to=franzschrober@yahoo.de \
    --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).