public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: why are some of my patches being credited to other "authors"?
Date: Sun, 10 Dec 2006 14:09:20 +0900	[thread overview]
Message-ID: <20061210050920.GA19828@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612090706500.13654@localhost.localdomain>

On Sat, Dec 09, 2006 at 07:11:21AM -0500, Robert P. J. Day wrote:
> 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.
> 
Trivial patches tend not to be a priority for most people, especially
during a period when people are gearing up for the close of the merge
window (unless they happen to fix a serious bug, in which case it's
another matter, and it should also be brought to -stable's attention).
Timing has a lot to do with expected feedback for these sorts of things.

trivial@kernel.org exists to handle the rest of the bits, where Adrian
has a tendency to queue up many trivial and related patches at once, and
sending out pull requests at a time where it will be less disruptive to
the rest of development. You might be better off simply CC'ing trivial@
on these patch submissions and routinely checking the trivial git tree to
see whether they've been queued or not.

However, if you're changing or reordering functionality that isn't an
obvious bugfix, you're still going to have to get an ack from the
maintainer.

  parent reply	other threads:[~2006-12-10  5:10 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
2006-12-09 12:11   ` Robert P. J. Day
2006-12-09 21:40     ` Stefan Richter
2006-12-10  5:09     ` Paul Mundt [this message]
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=20061210050920.GA19828@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=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