[lkml]   [2004]   [May]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFD] Explicitly documenting patch submission
On Tue, May 25, 2004 at 01:18:05PM -0400, Ben Collins wrote:

> I know you want this simple, but should we keep the paper-trail momentum
> going by adding a "Submitted-by"? Like if I get a one-liner fix, which
> is obviously not adding new code, rather than go through the whole
> process of asking for them to agree to the signoff deal, could I do:
> Submitted-by: Jimmy Janitor <jimmy@janitor.blah>
> Signed-off-by: Ben Collins <>
> ? I like the idea of knowing where a patch came from and via who. This
> would make it easier to analyze that info, but keep it simple for
> trivial patches that so many of us get (in the (b) case).

For trivial one liners, it's usually quicker for me to
just hack the file myself than to save the diff, run it through
patch, delete the diff when I'm done etc. When I do this
I usually put in the changelog "pointed out by Joe Hacker".
My reasoning behind this is that all typos are then mine 8-)
whilst still crediting the person who did the original.

Likewise if I fix something in a slightly different way
to how the patch that was submitted did it, as the person
reporting still did some work which they should be credited for,
even if ultimately their solution wasn't used, but was used
as a basis for the real fix.

In these cases, I think it'd be reasonable to have..

Signed-off-by: Dave Jones <>
Spotted-by: Joe Hacker <>

As asking submitters to sign off on modified versions
of their patch would be silly overhead IMO.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:03    [W:0.041 / U:3.680 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site