Re: [RFD] Explicitly documenting patch submission

[Ben Collins <bcollins@debian.org>]

On Tue, May 25, 2004 at 10:15:15AM -0700, Linus Torvalds wrote:
> 
> 
> On Tue, 25 May 2004, Ben Collins wrote:
> >
> > I've got a question about this. A lot of times I get patches that are
> > just one/two-liners and the explanation is somewhat self-explantory,
> > etc. Say the patch comes to me from some patch collection maintainer,
> > who got it from the original author.
> > 
> > So the original person never put a Signed-off-by, and neither did the
> > person who sent me the patch, should I still add the eplicit
> > Signed-off-by's to the patch, and add myself, before sending it to you?
> 
> You should never sign off for somebody else.
> 
> You _can_ sign off as yourself, and just add a note of "From xxxx". That's
> what the (b) case is all about (ie "to the best of my knowledge it's
> already under a open-source license").
> 
> Of course, if it's a _big_ work with lots of original content, and you're 
> unsure of exactly what the original author wanted to do with this, you 
> obviously should _not_ sign off on it. But you knew that.

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 <bcollins@debian.org>

? 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).

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/