From: Ric Wheeler <ric@emc.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <greg@kroah.com>, Roman Zippel <zippel@linux-m68k.org>,
linux-m68k@vger.kernel.org, geert@linux-m68k.org,
torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: License oddity in some m68k files
Date: Fri, 20 Jan 2006 08:45:01 -0500 [thread overview]
Message-ID: <43D0E95D.60802@emc.com> (raw)
In-Reply-To: <1137760499.24161.0.camel@localhost.localdomain>
Alan Cox wrote:
>On Gwe, 2006-01-20 at 07:21 -0500, Ric Wheeler wrote:
>
>
>>The language in the source files is pretty strong and this looks like
>>Motorola should be asked to rerelease the files with a normal
>>copyright notice in place of the current language...
>>
>>
>
>Its standard boilerplate from the period. Its a perfectly normal and
>clear copyright notice.
>
>Alan
>
>
Actually, that is the exact language our lawyers still give us to use
today when we have not settled on license terms when we want to share
code in a severely limited fashion.
I still think it best that they (Freescale) modify their language to
reference the actual license grant in the README.
ric
next prev parent reply other threads:[~2006-01-20 13:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 18:09 License oddity in some m68k files Greg KH
2006-01-19 19:05 ` Brad Boyer
2006-01-19 20:14 ` Roman Zippel
2006-01-19 22:04 ` Greg KH
2006-01-19 22:14 ` Alan Cox
2006-01-19 22:32 ` Greg KH
2006-01-20 12:21 ` Ric Wheeler
2006-01-20 12:34 ` Alan Cox
2006-01-20 13:45 ` Ric Wheeler [this message]
2006-01-20 14:49 ` Kumar Gala
2006-01-19 21:40 ` Alan Cox
2006-01-20 7:52 ` Jes Sorensen
2006-01-20 8:52 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2006-01-21 0:24 Matt Waddel
2006-01-21 0:36 ` Greg KH
2006-01-30 18:03 ` Alan Cox
2006-02-01 4:02 ` Matt Waddel
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=43D0E95D.60802@emc.com \
--to=ric@emc.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zippel@linux-m68k.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.