From: Nix <nix@esperi.org.uk>
To: omb@bluewin.ch
Cc: Patrick McFarland <pmcfarland@downeast.net>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Joerg Schilling flames Linux on his Blog
Date: Mon, 23 May 2005 15:58:06 +0100 [thread overview]
Message-ID: <87wtpqdm69.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <4291EA2D.60504@khandalf.com> (Brian O'Mahoney's message of "Mon, 23 May 2005 16:35:25 +0200")
On Mon, 23 May 2005, Brian O'Mahoney said:
> 1__
>
> The GPL says nothing about using a GPL, or non-free tool to create
> something else, and cannot since it is a copyright based licence.
The point of libgcc is that it is *linked in* to generated programs, and
thus under the FSF's interpretation might force those programs to be
covered by the GPL. Hence the exception, to make it clear that this is
not the case.
(It is even more necessary for the libstdc++ headers and Ada runtime,
as they are respectively textually included and included in cross-module
inlining...)
> 2__
>
> He has decided what the answer MUST be ... now the reasoning. Here we
> have a Solaris shill!
Nah, it's not that simple: apparently he flames them, too. I think we
can safely say he is no-one's pansy. (Now he might be impossible to
please, but that's a different matter.)
--
`Once again, I must remark on the far-reaching extent of my
ladylike nature.' --- Rosie Taylor
next prev parent reply other threads:[~2005-05-23 14:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 17:45 [OT] Joerg Schilling flames Linux on his Blog Patrick McFarland
2005-05-20 17:02 ` jmerkey
2005-05-20 18:24 ` Markus Plail
2005-05-20 18:34 ` Matthias-Christian Ott
2005-05-20 18:41 ` Lee Revell
2005-05-20 23:20 ` Brian O'Mahoney
2005-05-21 7:38 ` Adrian Bunk
2005-05-21 11:25 ` Bernd Petrovitsch
2005-05-21 11:33 ` Måns Rullgård
2005-05-22 18:24 ` Bernd Petrovitsch
2005-05-21 11:41 ` André Tomt
2005-05-21 23:24 ` Adrian Bunk
2005-05-22 0:27 ` Andre Tomt
2005-05-22 14:17 ` Matthias Andree
2005-05-21 16:39 ` Brian O'Mahoney
2005-05-21 23:59 ` Adrian Bunk
2005-05-22 1:22 ` Andrew Haninger
2005-05-22 4:23 ` [OT] Joerg Schilling flames Linux on his Blog/cdrecord replacement Brian O'Mahoney
2005-05-22 14:36 ` Matthias Andree
2005-05-22 17:42 ` Matthias Urlichs
2005-05-22 4:50 ` [OT] Joerg Schilling flames Linux on his Blog Patrick McFarland
2005-05-22 14:39 ` Matthias Andree
2005-05-22 20:40 ` Bernhard Rosenkraenzer
2005-05-22 15:54 ` Alistair John Strachan
2005-05-23 13:17 ` Nix
2005-05-23 14:35 ` Brian O'Mahoney
2005-05-23 14:58 ` Nix [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-25 13:15 OT] " Joerg Schilling
2005-05-25 23:12 ` Kyle Moffett
2005-05-26 10:15 ` Joerg Schilling
2005-05-26 12:47 ` [OT] " Alexander E. Patrakov
2005-05-27 10:31 ` Joerg Schilling
[not found] <4847F-8q-23@gated-at.bofh.it>
2005-05-25 22:46 ` OT] " Joerg Schilling
2005-05-25 23:31 ` Kyle Moffett
2005-05-26 3:45 ` [OT] " Alexander E. Patrakov
2005-05-26 5:06 ` Giuseppe Bilotta
[not found] ` <Pine.LNX.4.58.0505261335440.2939@be1.lrz>
2005-05-26 12:33 ` Alexander E. Patrakov
[not found] ` <Pine.LNX.4.58.0505261651220.3407@be1.lrz>
2005-05-27 10:44 ` Joerg Schilling
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=87wtpqdm69.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=omb@bluewin.ch \
--cc=pmcfarland@downeast.net \
/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