From: Ralf Baechle <ralf@linux-mips.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Martin Michlmayr <tbm@cyrius.com>, linux-mips@linux-mips.org
Subject: Re: MIPS contributions have "All rights reserved"?
Date: Sat, 22 Jan 2005 19:21:55 +0000 [thread overview]
Message-ID: <20050122192155.GA1004@linux-mips.org> (raw)
In-Reply-To: <1106159183.3341.4.camel@localhost.localdomain>
On Wed, Jan 19, 2005 at 10:39:59PM +0000, Alan Cox wrote:
> > > - * Copyright (C) 2000, 2004 MIPS Technologies, Inc. All rights reserved.
> > > + * Copyright (C) 2000, 2004, 2005 MIPS Technologies, Inc.
> > > + * All rights reserved.
> >
> > Does this "All rights reserved" statement make sense in a kernel which
> > is GPL?
>
> Providing it also says its GPL licensed why not. You reserve all your
> rights then license some.
It's been a repeated cause of confusion and the MIPS port had them in 120
files, so with permission I removed the "All rights reserved." of 40 of
them. The remaining 80 will probably stay as they are.
Ralf
prev parent reply other threads:[~2005-01-22 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050119024536Z8225221-1340+1568@linux-mips.org>
2005-01-19 13:42 ` MIPS contributions have "All rights reserved"? Martin Michlmayr
2005-01-19 22:39 ` Alan Cox
2005-01-22 19:21 ` Ralf Baechle [this message]
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=20050122192155.GA1004@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@linux-mips.org \
--cc=tbm@cyrius.com \
/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