Krzysztof Halasa wrote: > Ben Hutchings <b...@decadent.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 <david...@tmr.com> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
