From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] radeon_cp: use request_firmware
Date: Tue, 14 Apr 2009 17:06:16 -0400 [thread overview]
Message-ID: <49E4FAC8.1000804@tmr.com> (raw)
In-Reply-To: <m3bpqzuw50.fsf@intrepid.localdomain>
Krzysztof Halasa wrote:
> Ben Hutchings <ben@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 <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2009-04-14 21:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 16:27 [PATCH] radeon_cp: use request_firmware Jaswinder Singh Rajput
2009-04-13 18:26 ` Ben Hutchings
2009-04-14 4:54 ` Jaswinder Singh Rajput
2009-04-14 14:26 ` Ben Hutchings
2009-04-14 14:50 ` Krzysztof Halasa
2009-04-14 21:06 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 7:51 Jaswinder Singh
2008-08-07 10:24 ` Gene Heskett
2008-08-07 17:04 ` Jaswinder Singh
2008-12-19 20:23 ` Jaswinder Singh
2008-12-21 20:58 ` Dave Airlie
2008-12-22 10:39 ` Julien Cristau
2008-12-23 14:53 ` Ben Hutchings
2008-12-30 3:02 ` Jaswinder Singh Rajput
2008-12-22 11:27 ` Jaswinder Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E4FAC8.1000804@tmr.com \
--to=davidsen@tmr.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.