| 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: <49E4FAC8.1000804@tmr.com> Date: Tue, 14 Apr 2009 17:06:16 -0400 From: Bill Davidsen <davidsen@....com> To: linux-kernel@...r.kernel.org Cc: dri-devel@...ts.sourceforge.net Subject: Re: [PATCH] radeon_cp: use request_firmware Krzysztof Halasa wrote: > Ben Hutchings <ben@...adent.org.uk> writes: > >> I don't copy Signed-off-by if I make significant changes as the original >> author should not be held responsible for any errors. I'll be happy to >> ask for your S-o-b before submitting a patch based on your work in future. > > I think we should never include the original SOB if there was _any_ > change. SOB is not credits, it's a signature. If someone takes my patch > and changes it, I want my SOB line removed unless I re-sign the modified > patch. > > We may invent some other Based-on-patch-by: etc. tag if really > necessary, but the signature is a different thing. Given that this is the 2nd or 3rd instance of someone feeling that their code has been used without credit, that may be a good idea. I certainly can see the point, having had a significant effort of mine lightly patched and then given to FSF without my name on it. -- Bill Davidsen <davidsen@....com> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- 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