From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Jeff Garzik <jeff@garzik.org>
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, 9 Dec 2006 07:11:21 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612090706500.13654@localhost.localdomain> (raw)
In-Reply-To: <457A9F3B.6020009@garzik.org>
On Sat, 9 Dec 2006, Jeff Garzik wrote:
> 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.
and just to finish off this still-twitching horse, i'm not that
concerned if someone else gets the attribution. that patch was so
trivial, it's not like i'm going to parade it around as my
contribution to the kernel. (and, as i said, it's entirely possible
that this was just one of those wild coincidences.)
i'm far more interested in at least knowing what happens to patches
once they enter the system, so i can plan on what kind of cleanup i
can work on next.
rday
next prev parent reply other threads:[~2006-12-09 12:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 10:22 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
2006-12-09 12:11 ` Robert P. J. Day [this message]
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=Pine.LNX.4.64.0612090706500.13654@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®