public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: why are some of my patches being credited to other "authors"?
Date: Sat, 09 Dec 2006 06:34:19 -0500	[thread overview]
Message-ID: <457A9F3B.6020009@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612090515480.12992@localhost.localdomain>

Robert P. J. Day wrote:
>   i've submitted a number of patches recently and, every time i do a
> "git pull", i check the log to see if any of them have been applied so
> i can delete them from my personal "submitted but not applied"
> directory.  if they've been applied by another author, then naturally
> i'll never notice and i'll keep wondering about the delay.
> 
>   so what's the protocol here?  are more senior kernel developers
> allowed to poach on my patch submissions, tidy them up slightly, then
> drop any attribution to me?  enquiring minds *definitely* want this
> cleared up.
> 
> rday
> 
> p.s.  it's possible that this is all just a wild coincidence, of
> course.  stranger things have happened.


The protocol is simply to do best to give credit where credit is due. 
If your patch is taken directly, most likely it is a mistake if 
attribution was dropped.  If your patch was modified, often that patch 
will get checked in under the name of the person who last touched the 
change before commit -- and it is their responsibility to make sure and 
note that the change originally came from you.

	Jeff



  parent reply	other threads:[~2006-12-09 11:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09 10:22 why are some of my patches being credited to other "authors"? Robert P. J. Day
2006-12-09 11:29 ` Benjamin Herrenschmidt
2006-12-09 12:05   ` Robert P. J. Day
2006-12-09 12:39     ` Tim Schmielau
2006-12-09 13:16       ` Robert P. J. Day
2006-12-09 13:55         ` Jesper Juhl
2006-12-09 11:34 ` Jeff Garzik [this message]
2006-12-09 12:11   ` Robert P. J. Day
2006-12-09 21:40     ` Stefan Richter
2006-12-10  5:09     ` Paul Mundt
2006-12-10 19:19       ` Adrian Bunk
2006-12-09 13:48 ` Pekka Enberg
2006-12-10  7:24 ` Andrew Morton

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=457A9F3B.6020009@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.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