linux-kernel - Re: why are some of my patches being credited to other "authors"?

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:	Sat, 09 Dec 2006 22:40:55 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
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"?

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.

The maintainers handle this differently. If you don't get feedback nor
see your patch appearing in the maintainer's repo after a while, just ask
what happened or repost your patch (with a [resend] flag or a respective
note below the patch description).
-- 
Stefan Richter
-=====-=-==- ==-- -=--=
http://arcgraph.de/sr/
-
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/