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 06:34:19 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
CC:	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've submitted a number of patches recently and, every time i do a
> "git pull", i check the log to see if any of them have been applied so
> i can delete them from my personal "submitted but not applied"
> directory.  if they've been applied by another author, then naturally
> i'll never notice and i'll keep wondering about the delay.
> 
>   so what's the protocol here?  are more senior kernel developers
> allowed to poach on my patch submissions, tidy them up slightly, then
> drop any attribution to me?  enquiring minds *definitely* want this
> cleared up.
> 
> rday
> 
> p.s.  it's possible that this is all just a wild coincidence, of
> course.  stranger things have happened.


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.

	Jeff


-
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