From: Ric Wheeler <ric@emc.com>
To: Greg KH <greg@kroah.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
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 07:21:00 -0500 [thread overview]
Message-ID: <43D0D5AC.2010604@emc.com> (raw)
In-Reply-To: <20060119223251.GB27106@kroah.com>
Greg KH wrote:
>On Thu, Jan 19, 2006 at 10:14:56PM +0000, Alan Cox wrote:
>
>
>>On Iau, 2006-01-19 at 14:04 -0800, Greg KH wrote:
>>
>>
>>>Ah, ok, thanks, that makes sense. How about a simple pointer to the
>>>license info from the .S files to the README file so that people (like
>>>me), don't get confused again? I've attached a patch below if you wish
>>>to apply it.
>>>
>>>
>>>
>>They specifically ask as is their right within the GPL that you note if
>>you modify the files. Otherwise seems fine.
>>
>>
>
>Hm, any idea on how to note that I modified the file in such a way that
>would be acceptable? How about this?
>
>+|
>+| For details on the license for this file, please see the
>+| file, README, in this same directory. Note, this paragraph in
>+| this comment has been added from the original version of this
>+| file from the author.
>
>thanks,
>
>greg k-h
>
>
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...
ric
next prev parent reply other threads:[~2006-01-20 12:23 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 [this message]
2006-01-20 12:34 ` Alan Cox
2006-01-20 13:45 ` Ric Wheeler
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=43D0D5AC.2010604@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.