public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 20:03:44 +0100	[thread overview]
Message-ID: <20050522200344.B9854@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1116787877.6285.26.camel@laptopd505.fenrus.org>; from arjan@infradead.org on Sun, May 22, 2005 at 08:51:17PM +0200

On Sun, May 22, 2005 at 08:51:17PM +0200, Arjan van de Ven wrote:
> On Sun, 2005-05-22 at 19:44 +0100, Russell King wrote:
> > 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.
> 
> 
> author David Woodhouse <dwmw2@org.rmk.(none)> Sat, 21 May 2005 15:52:23 +0100
> 
> that looks far more like an authorship statement and is also munged.

In which case we have a problem:

http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=12f49643bc44c428919b210148a930496827dd26

Therefore, I put forward that this thing which appears to be called
"author" does not reflect authorship, but who submitted it.

Alternatively, if you are right, we must not wrongfully claim people
"author" code in this way, and the above log entry needs fixing.
Since that's not possible, we must refuse patches from people who
aren't themselves the authors of the submitted code.  But how do we
positively know that in every case?

That's another very interesting problem you've just brought up with
public project systems.  And of course now that it's been identified
it needs addressing.  8(

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-05-22 19:03 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
2005-05-22 18:51         ` Arjan van de Ven
2005-05-22 19:03           ` Russell King [this message]
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=20050522200344.B9854@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