From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: When we detect that a 16550 was in fact part of a NatSemi SuperIO chip
Date: Sun, 22 May 2005 19:44:38 +0100 [thread overview]
Message-ID: <20050522194438.A9854@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1116785646.6285.24.camel@laptopd505.fenrus.org>; from arjan@infradead.org on Sun, May 22, 2005 at 08:14:06PM +0200
On Sun, May 22, 2005 at 08:14:06PM +0200, Arjan van de Ven wrote:
> On Sun, 2005-05-22 at 09:59 -0700, Linus Torvalds wrote:
> >
> > On Sun, 22 May 2005, David Woodhouse wrote:
> > >
> > > Linus, please do not apply patches from me which have my personal
> > > information mangled or removed.
> >
> > I've asked Russell not to do it, but the fact is, he's worried about legal
> > issues, and while I've also tried to resolve those (by having the OSDL
> > lawyer try to contact some lawyers in the UK), that hasn't been clarified
> > yet.
>
> there is a potential nasty interaction with the UK moral rights thing
> where an author can demand that his authorship claim remains intact...
> so if David objects to his authorship being mangled (and partially
> removed) he may have a strong legal position to do so.
Actually, that only depends on whether you decide that Signed-off-by:
reflects authorship. There's evidence to say that it may not:
1. There can be multiple Signed-off-by: lines in a patch - many of whom
are not authors of the code.
2. The first Signed-off-by: line may not be the author of the code if
the author has not added that himself. It may be a subsystem
maintainers.
If you don't believe either of those, I suggest you re-read the original
discussions about Signed-off-by: and refresh your memory that, in fact,
all Signed-off-by: is saying is that _someone_ accepts responsibility
for submitting the patch.
If you still don't accept that, here's the actual text in
SubmittingPatches - maybe it's wrong?
| The sign-off is a simple line at the end of the explanation for the
| patch, which certifies that you wrote it or otherwise have the right to
^^^^^^^^^^^^^^^^^^^^^^^^^^^
| pass it on as a open-source patch.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Let's look at it another way. Signed-off-by: is a mark of attributation
and authorship. If someone were to receive an un-signedoff patch but
had the right to pass it on as an open-source patch, according to your
position it would be wrong to add a "Signed-off-by:" line, because that's
like falsely claiming your the author of the code. And what about all
the other Signed-off-by: lines which are subsequently added by Andrew
and Linus? Aren't they falsely claiming authorship as well?
Therefore, claiming that Signed-off-by: is a mark of attributation
or authorship is obviously nonsense.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-05-22 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505220008.j4M08uE9025378@hera.kernel.org>
2005-05-22 11:57 ` When we detect that a 16550 was in fact part of a NatSemi SuperIO chip David Woodhouse
2005-05-22 12:59 ` Russell King
2005-05-22 13:23 ` David Woodhouse
2005-05-22 13:41 ` Russell King
2005-05-22 14:14 ` David Woodhouse
2005-05-22 21:16 ` Alan Cox
2005-05-22 21:50 ` Linus Torvalds
2005-05-22 22:22 ` Alan Cox
2005-05-22 22:40 ` Linus Torvalds
2005-05-22 22:43 ` Alan Cox
2005-05-23 4:09 ` Willy Tarreau
2005-05-23 5:15 ` Dmitry Torokhov
2005-05-23 7:21 ` Willy Tarreau
2005-05-23 14:27 ` Linus Torvalds
2005-05-22 16:59 ` Linus Torvalds
2005-05-22 17:15 ` David Woodhouse
2005-05-22 18:14 ` Arjan van de Ven
2005-05-22 18:44 ` Russell King [this message]
2005-05-22 18:51 ` Arjan van de Ven
2005-05-22 19:03 ` Russell King
2005-05-22 20:31 ` Linus Torvalds
2005-05-22 20:55 ` Brian O'Mahoney
2005-05-22 19:58 ` Brian O'Mahoney
2005-05-22 20:31 ` Lee Revell
2005-05-22 20:48 ` Linus Torvalds
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=20050522194438.A9854@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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