linux-kernel - Re: [PATCH] MAINTTAINERS: update DCO info

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Aug 2007 16:00:32 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Joe Perches <joe@...ches.com>
CC:	lkml <linux-kernel@...r.kernel.org>,
	torvalds <torvalds@...ux-foundation.org>,
	akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH] MAINTTAINERS: update DCO info

Joe Perches wrote:
> On Wed, 2007-08-22 at 08:24 -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@...cle.com>
>>
>> Update URL for DCO (old URL is invalid).
>> Also, point to SubmittingPatches for the current DCO.
>>
>> Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
>> ---
>>  MAINTAINERS |    5 ++++-
>>  1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> --- linux-2.6.23-rc3-git2.orig/MAINTAINERS
>> +++ linux-2.6.23-rc3-git2/MAINTAINERS
>> @@ -45,8 +45,11 @@ trivial patch so apply some common sense
>>  
>>  	PLEASE remember that submissions must be made under the terms
>>  	of the OSDL certificate of contribution
>> -	(http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html)
>> +	(http://old.linux-foundation.org/newsroom/press_releases/2004/2004_05_24_dco.html)
>>  	and should include a Signed-off-by: line.
>> +	The current certificate is also documented in
>> +	Documentation/SubmittingPatches as the Developer's Certificate
>> +	of Origin (DCO).
> 
> Why have an external link which may go out of date
> when we already have the cert?
> 
> It's really short, we could just quote it.

I wouldn't bother repeating it, but I'll happily remove the URL
and just refer to Documentation/SubmittingPatches.  I think that
the latter is a good place for it to stay.


> Maybe it should be a separate file
> Documentation/Developer_Certificate_of_Origin
> and referenced directly.
> 
> 	Developer's Certificate of Origin 1.1
> 
> 	By making a contribution to this project, I certify that:
> 
> 	(a) The contribution was created in whole or in part by me and I
> 	    have the right to submit it under the open source license
> 	    indicated in the file; or
> 
> 	(b) The contribution is based upon previous work that, to the best
> 	    of my knowledge, is covered under an appropriate open source
> 	    license and I have the right under that license to submit that
> 	    work with modifications, whether created in whole or in part
> 	    by me, under the same open source license (unless I am
> 	    permitted to submit under a different license), as indicated
> 	    in the file; or
> 
> 	(c) The contribution was provided directly to me by some other
> 	    person who certified (a), (b) or (c) and I have not modified
> 	    it.
> 
> 	(d) I understand and agree that this project and the contribution
> 	    are public and that a record of the contribution (including all
> 	    personal information I submit with it, including my sign-off) is
> 	    maintained indefinitely and may be redistributed consistent with
> 	    this project or the open source license(s) involved.
> 
> 


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/