From: Baurjan Ismagulov <ibr@radix50.net>
To: sparclinux@vger.kernel.org
Subject: Re: FPU context switching fix for SMP
Date: Sat, 29 Jan 2005 18:22:36 +0000 [thread overview]
Message-ID: <20050129182236.GE11528@radix50.net> (raw)
In-Reply-To: <41f753cabb795@wp.pl>
On Wed, Jan 26, 2005 at 03:09:51PM -0800, David S. Miller wrote:
> On Wed, 26 Jan 2005 23:06:41 +0100 Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr> wrote:
> > On Wed, Jan 26, 2005 at 12:26:10AM -0800, William Lee Irwin III wrote:
> > > Are you sure a bugfix merits a copyright attribution? It's atypical
> > > elsewhere...
> >
> > IANAL, but as I understand section 2 of GPL, it requires that any
> > changes are logged.
>
> It's only relevant if it is significant enough for copyright purposes.
> Changes or bug fixes that are only 2 or 3 lines in nature, generally
> aren't.
Ok, then our legal dept. interprets the license too literally :) .
> 1) copyright law and licensing are two different things, don't confuse
> them
Sure. The OP hasn't claimed copyright, he's just put a modification
notice. As he distributes his modification, however, he has to comply
with the GPL, which doesn't say that 2a applies to legally significant
changes only, that is why I wrote my previous e-mail.
Thanks for the explanations!
With kind regards,
Baurjan.
next prev parent reply other threads:[~2005-01-29 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 8:24 FPU context switching fix for SMP Krzysztof Helt
2005-01-26 8:26 ` William Lee Irwin III
2005-01-26 8:57 ` Krzysztof Helt
2005-01-26 22:06 ` Baurjan Ismagulov
2005-01-26 23:09 ` David S. Miller
2005-01-29 18:22 ` Baurjan Ismagulov [this message]
2005-02-15 17:40 ` David S. Miller
2005-02-15 20:01 ` William Lee Irwin III
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=20050129182236.GE11528@radix50.net \
--to=ibr@radix50.net \
--cc=sparclinux@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.