lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 10 Dec 2006 14:09:20 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	Jeff Garzik <jeff@...zik.org>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: why are some of my patches being credited to other "authors"?

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@...nel.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ