From: Samium Gromoff <deepfire@ibe.miee.ru>
To: andre@linux-ide.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Switching to the OSL License, in a dual way.
Date: Thu, 24 Jul 2003 14:35:58 +0400 [thread overview]
Message-ID: <87smow5i0h.wl%deepfire@ibe.miee.ru> (raw)
> Yeah the bit about "Nasal Sex with Dead Plants" just makes one wonder, is
> a rose just a rose? (note to self, don't read RMS's diary again)
Uhhuh, have you people lost your sense o humour?
Did actually _anyone_ red the Texan history rms describes on his site?
I personally find the history (where rms was denied to continue his
lisp machine lectures given that absurd excuse he was commiting a
nasal sex with dead plants) quite amusing...
But here you go, just care to read it before commenting.
Besides all i find rms diary rather interesting.
>
> Has anyone ever asked why it is okay for RMS to suggest it is okay to
> invalidate another person/company license (BitKeeper is the example) yet
I`m sure there is a link to a such his statement archived on the web.
Google returns too much results to be useful, so i`d be rather delighted
if you provide me with en exact link to this his statement.
> become offended when their own license is to desired to be invalidated?
>
> Why is it that nothing but gpl can exist with gpl?
>
> Why is that a superior option to license under which follows the
> original spirit of GPL but goes further to promote the ideas of open
> source is frowned upon?
Do yo mean rms reacted negatively to the existence of OSL?
I`m interested in that.
>
> Maybe it has something to do with self pollenation.
>
> Cheers,
>
> Andre Hedrick
> LAD Storage Consulting Group
regards, Samium Gromoff
next reply other threads:[~2003-07-24 11:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 10:35 Samium Gromoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-26 20:20 Switching to the OSL License, in a dual way John Bradford
2003-07-26 19:46 Hank Leininger
2003-07-25 15:33 John Bradford
2003-07-25 15:36 ` Valdis.Kletnieks
2003-07-25 9:34 Samium Gromoff
2003-07-25 13:27 ` Gaël Le Mignot
2003-07-24 11:51 Dean McEwan
2003-07-24 22:25 ` Stefan Reinauer
2003-07-24 8:40 Dean McEwan
2003-07-24 8:58 ` Miles Bader
2003-07-24 9:46 ` Andre Hedrick
2003-07-24 18:06 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 20:02 ` Andre Hedrick
2003-07-24 21:05 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 21:57 ` Larry McVoy
2003-07-24 22:24 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-25 9:56 ` Gaël Le Mignot
2003-07-25 14:39 ` Larry McVoy
2003-07-26 2:52 ` Matthias Andree
2003-07-26 3:18 ` Larry McVoy
2003-07-25 13:17 ` Jesse Pollard
2003-07-25 14:55 ` Larry McVoy
2003-07-25 15:15 ` Gaël Le Mignot
2003-07-25 15:33 ` Richard B. Johnson
2003-07-26 19:10 ` Rik van Riel
2003-07-26 19:23 ` Larry McVoy
2003-07-26 19:46 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-26 20:01 ` Larry McVoy
2003-07-26 21:08 ` Mr. James W. Laferriere
2003-07-26 20:21 ` Bernd Eckenfels
2003-07-24 9:05 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-27 9:21 ` Kai Henningsen
2003-07-24 11:30 ` viro
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=87smow5i0h.wl%deepfire@ibe.miee.ru \
--to=deepfire@ibe.miee.ru \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.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).