public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Alexander Terekhov" <TEREKHOV@de.ibm.com>
To: "Phil Frisbie, Jr." <phil@hawksoft.com>
Cc: Nedko Arnaudov <nedko.arnaudov@atia.com>,
	pthreads-win32@sources.redhat.com
Subject: Re: Windows kernel-mode implementation of pthreads
Date: Fri, 09 Jan 2004 18:13:00 -0000	[thread overview]
Message-ID: <OF89146050.D435BE21-ONC1256E16.0064754F-C1256E16.00640E07@de.ibm.com> (raw)
In-Reply-To: <3FFEE036.7000504@hawksoft.com>

"Phil Frisbie, Jr." wrote:
[...]
> > If not (expected), will it be violation of LGPL 
> > if I use code from pthreads-win32 in kernel mode
> > driver for Windows ?
>
> If you need to 'cut and paste' then you will need 
> to publish your source code, ...

Not necessarily.

http://digital-law-online.info/lpdi1.0/treatise9.html

<quote>

II.E.2. Idea-Expression Merger and Scènes À Faire

When there are only a limited number of ways that a 
concept or idea can be expressed, there is little 
difference between the idea and its expression, and 
it is therefore said that the two have "merged." 
When this happens, the limited number of ways of 
expressing the idea are not entitled to copyright 
protection because, in essence, that would be 
protecting the idea, something outside the scope of 
copyright. The merger doctrine means that even if 
things are substantially similar, or even identical, 
there might not be a copyright infringement.

</quote>

regards,
alexander.

  reply	other threads:[~2004-01-09 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 16:58 Nedko Arnaudov
2004-01-09 17:09 ` Phil Frisbie, Jr.
2004-01-09 18:13   ` Alexander Terekhov [this message]
2004-01-09 18:03 ` Alexander Terekhov

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=OF89146050.D435BE21-ONC1256E16.0064754F-C1256E16.00640E07@de.ibm.com \
    --to=terekhov@de.ibm.com \
    --cc=nedko.arnaudov@atia.com \
    --cc=phil@hawksoft.com \
    --cc=pthreads-win32@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).