From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] generic arm for MSM try2
Date: Mon, 29 Mar 2010 11:20:34 -0700 [thread overview]
Message-ID: <1269886834.17124.24.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100329181717.GA15163@atrey.karlin.mff.cuni.cz>
On Mon, 2010-03-29 at 20:17 +0200, Pavel Machek wrote:
> Hi!
>
> > > > >
> > > > > 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.
> >
> > Before we discuss it lets just be clear that I've already offered to
> > remove the copyright, and license changes.. I've not said that I
> > wouldn't do that , in fact I'll make a new pull request now minus those.
> >
> > > 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.
> >
> > There is git history on it. Anyone that looks at the git history would
> > know right off we didn't write the whole file. There's nothing stopping
> > other copyright holders from adding their copyright on top of ours.
> Maybe sane solution is to write "portions copyright"? people will not
> dig into git history when there's just one author listed.
I tried that in the generic kernel once, and Andrew told me to remove
those parts because we had git history for that.. So I don't know, maybe
we need to require boiler plate copyrights on all files, and fix ones
that don't already have them.
Daniel
next prev parent reply other threads:[~2010-03-29 18:20 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
2010-03-29 17:44 ` Daniel Walker
2010-03-29 18:17 ` Pavel Machek
2010-03-29 18:20 ` Daniel Walker [this message]
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=1269886834.17124.24.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--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).