From: Jiri Slaby <jirislaby@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: License violation?
Date: Fri, 02 Mar 2007 02:07:20 +0100 [thread overview]
Message-ID: <45E778C8.8020500@gmail.com> (raw)
In-Reply-To: <45E771D9.90003@goop.org>
Jeremy Fitzhardinge napsal(a):
> 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.
Nice to hear this, thanks,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
Hnus <hnus@fi.muni.cz> is an alias for /dev/null
next prev parent reply other threads:[~2007-03-02 1:07 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
2007-03-02 1:07 ` Jiri Slaby [this message]
[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=45E778C8.8020500@gmail.com \
--to=jirislaby@gmail.com \
--cc=jeremy@goop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.