linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] generic arm for MSM try2
Date: Mon, 29 Mar 2010 18:28:42 +0100	[thread overview]
Message-ID: <20100329172841.GD28468@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1269881777.17124.5.camel@c-dwalke-linux.qualcomm.com>

On Mon, Mar 29, 2010 at 09:56:17AM -0700, Daniel Walker wrote:
> On Sun, 2010-03-28 at 22:49 +0100, Russell King - ARM Linux wrote:
> > On Thu, Mar 25, 2010 at 04:35:55PM -0700, Daniel Walker wrote:
> > > Ok, attempt #2 .. It's the same set of patches , only it's against
> > > mainline linus tree of the moment. I force updated it into the same
> > > "for-russell" branch.
> > > 
> > > btw, you might want to pay close attention to the "Fix incorrect
> > > permission faults" patch. That's the only non-small patch in the queue.
> > 
> > Well, I don't think it's fair on those who created abort-ev7.S to go
> > throwing a boilerplate copyright on the file which makes it look like
> > "Code Aurora Forum." wrote the entire thing.
> 
> You want the license and copyright removed? I can remove them, although
> I rather not have too.

The fact of the matter is that "Code Aurora Forum" did not create this
file, and their copyright does not cover the code which is already there.

By putting such a boilerplate at the start of the file without some
acknowledgement of its past history, they are effectively saying that
their copyright extends to everything in the file.  That's certainly
not the case; take a moment to consider how you'd feel if someone threw
their copyright boilerplate on a file you'd written.

Personally, I think this practice (adding copyright headers to pre-
existing files not authored by those claiming copyright ) is equivalent
to code theft.

It's far better to leave files without copyright headers if they start
out like that, or locate the original authors (Catalin) and have them
add a header.

Catalin, as the apparant author of this file, do you have a view on this?

  reply	other threads:[~2010-03-29 17:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 23:35 [GIT PULL] generic arm for MSM try2 Daniel Walker
2010-03-28 21:49 ` Russell King - ARM Linux
2010-03-28 23:51   ` Nicolas Pitre
2010-03-29 16:55     ` Daniel Walker
2010-03-29 16:56   ` Daniel Walker
2010-03-29 17:28     ` Russell King - ARM Linux [this message]
2010-03-29 17:44       ` Daniel Walker
2010-03-29 18:17         ` Pavel Machek
2010-03-29 18:20           ` Daniel Walker
2010-03-29 18:51         ` Nicolas Pitre
2010-03-29 19:07           ` Daniel Walker
2010-03-29 19:18             ` Nicolas Pitre
2010-03-29 20:27       ` Daniel Walker
2010-03-29 21:50         ` Catalin Marinas
2010-03-29 22:10           ` Daniel Walker
2010-03-30  9:57             ` Catalin Marinas
2010-03-30 12:57               ` Nicolas Pitre
2010-03-29 22:30           ` Daniel Walker
2010-03-30 22:59   ` Daniel Walker

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=20100329172841.GD28468@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).