| 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
| ||
|
Message-ID: <Pine.LNX.4.64.0612090706500.13654@localhost.localdomain> Date: Sat, 9 Dec 2006 07:11:21 -0500 (EST) From: "Robert P. J. Day" <rpjday@...dspring.com> To: Jeff Garzik <jeff@...zik.org> cc: Linux kernel mailing list <linux-kernel@...r.kernel.org> Subject: Re: why are some of my patches being credited to other "authors"? 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 - 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