Message ID | 1385633782-775-5-git-send-email-franzschrober@gmail.com (mailing list archive) |
---|---|
State | Superseded, archived |
Headers | show |
On Thu, Nov 28, 2013 at 11:16:21AM +0100, Franz Schrober wrote: > From: Franz Schrober <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". This previous section on "Why not GPL?" is now inaccurate as well; the last paragraph no longer applies, given the MIT license. - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
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
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. - - Q. Does it really parse C? A. Yeah, well... It parses a fairly complete subset of "extended C" as