From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: License violation?
Date: Thu, 01 Mar 2007 16:37:45 -0800 [thread overview]
Message-ID: <45E771D9.90003@goop.org> (raw)
In-Reply-To: <45E77176.7070200@gmail.com>
Jiri Slaby wrote:
> No other text in there, but simple Copyright:
>
> /* Copyright (c) 1997-2002 Sensable Technologies, Inc.
> All rights reserved.
Well, I think that means you can use info from that file to make your's
better, but you can't copy actual code.
J
next prev parent reply other threads:[~2007-03-02 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 0:13 License violation? Jiri Slaby
2007-03-02 0:31 ` Jeremy Fitzhardinge
2007-03-02 0:36 ` Jiri Slaby
2007-03-02 0:37 ` Jeremy Fitzhardinge [this message]
2007-03-02 1:07 ` Jiri Slaby
[not found] ` <45E77931.5090005@goop.org>
2007-03-02 1:27 ` Jiri Slaby
2007-03-02 12:41 ` Alan
2007-03-02 20:43 ` Jiri Slaby
2007-03-02 21:18 ` David Schwartz
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=45E771D9.90003@goop.org \
--to=jeremy@goop.org \
--cc=jirislaby@gmail.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