From: "D. Stimits" <stimits@idcomm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Controversy over dynamic linking -- how to end the panic
Date: Thu, 21 Jun 2001 14:17:41 -0600 [thread overview]
Message-ID: <3B325665.346F5AB5@idcomm.com> (raw)
In-Reply-To: <E15D9mV-0001wf-00@the-village.bc.nu> <p05100327b757fc43c456@[207.213.214.37]>
Jonathan Lundell wrote:
>
> At 8:06 PM +0100 2001-06-21, Alan Cox wrote:
> > > > the stdio.h, I'd tell him to go screw himself.
> >> What is the difference between including kernel header file and
> >> including GPLed header file?
> >
> >There are real differences between programs and interface definitions. At this
> >point you get into law and the like and its probably best you read up on it
> >from a reputable source not l/k
>
> Though header files don't fall clearly on the interface-definition
> side of the line. ctype.h, for example, in userland, or any other
> header with #defined or inline code.
> --
> /Jonathan Lundell.
Add to that the complications of C++ templates (not used in kernel, but
it could certainly test the law).
next prev parent reply other threads:[~2001-06-21 20:16 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 18:14 Controversy over dynamic linking -- how to end the panic Eric S. Raymond
2001-06-21 18:30 ` Alan Cox
2001-06-21 19:17 ` Eric S. Raymond
2001-06-21 19:51 ` Andrew Pimlott
2001-06-21 20:13 ` Eric S. Raymond
2001-06-21 20:17 ` David S. Miller
2001-06-21 20:46 ` Andrew Pimlott
2001-06-21 21:02 ` Timur Tabi
2001-06-21 21:05 ` Andrew Pimlott
2001-06-21 21:17 ` Timur Tabi
2001-06-21 20:29 ` Timur Tabi
2001-06-21 18:39 ` Jeff Golds
2001-06-21 18:51 ` Jeff Mahoney
2001-06-21 20:02 ` Steve Brueggeman
2001-06-21 18:46 ` Timur Tabi
2001-06-21 19:03 ` Timur Tabi
2001-06-21 19:53 ` Erik Mouw
2001-06-21 19:04 ` Mike Harrold
2001-06-21 19:14 ` Alan Cox
2001-06-21 20:12 ` Marco Colombo
2001-06-21 21:14 ` Alan Cox
2001-06-21 20:31 ` Timur Tabi
2001-06-21 19:08 ` Timur Tabi
2001-06-21 19:17 ` Alexander Viro
2001-06-21 20:01 ` Wei Weng
2001-06-21 19:06 ` Alan Cox
2001-06-21 19:34 ` Jonathan Lundell
2001-06-21 20:17 ` D. Stimits [this message]
2001-06-22 11:32 ` Rob Landley
2001-06-21 20:34 ` Craig Milo Rogers
2001-06-21 21:35 ` Controversy over dynamic linking -- how to end the panic (long) Alex Bligh - linux-kernel
2001-06-22 12:32 ` Fair Use (Was Re: Controversy over dynamic linking -- how to end the panic) Rob Landley
2001-06-22 1:29 ` Controversy over dynamic linking -- how to end the panic Andrea Arcangeli
2001-06-22 10:44 ` David Woodhouse
2001-06-23 20:11 ` Fabrice Gautier
-- strict thread matches above, loose matches on Subject: below --
2001-06-21 19:22 Disconnect
2001-06-21 19:24 ` Alan Cox
2001-06-21 19:25 Jesse Pollard
2001-06-21 21:43 Timur Tabi
2001-06-22 3:05 Rick Hohensee
2001-06-22 4:05 ` kumon
2001-06-23 22:29 ` Scott Wood
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=3B325665.346F5AB5@idcomm.com \
--to=stimits@idcomm.com \
--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