[PATCH] MAINTTAINERS: update DCO info

Previous thread: Linux Foundation Technical Advisory Board Elections by James Bottomley on Wednesday, August 22, 2007 - 8:22 am. (62 messages)

Next thread: Patch for Apani Nortel VPN Client to build against kernel 2.6.22 help/review by Fortier,Vincent [Montreal] on Wednesday, August 22, 2007 - 8:38 am. (3 messages)
From: Randy Dunlap
Date: Wednesday, August 22, 2007 - 8:24 am

From: Randy Dunlap <randy.dunlap@oracle.com>

Update URL for DCO (old URL is invalid).
Also, point to SubmittingPatches for the current DCO.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.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).
 
 6.	Make sure you have the right to send any changes you make. If you
 	do changes at work you may find your employer owns the patch
-

From: Joe Perches
Date: Wednesday, August 22, 2007 - 3:57 pm

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.

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.


-

From: Randy Dunlap
Date: Wednesday, August 22, 2007 - 4:00 pm

I wouldn't bother repeating it, but I'll happily remove the URL
and just refer to Documentation/SubmittingPatches.  I think that


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-

From: Randy Dunlap
Date: Thursday, August 23, 2007 - 11:50 pm

From: Randy Dunlap <randy.dunlap@oracle.com>

Drop the URL for DCO (URL is invalid).
Also, point to SubmittingPatches for the current DCO.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 MAINTAINERS |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

--- linux-2.6.23-rc3-git6.orig/MAINTAINERS
+++ linux-2.6.23-rc3-git6/MAINTAINERS
@@ -44,9 +44,10 @@ trivial patch so apply some common sense
 	or does something very odd once a month document it.
 
 	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)
-	and should include a Signed-off-by: line.
+	of the OSDL certificate of contribution and should include a
+	Signed-off-by: line.  The current version of this "Developer's
+	Certificate of Origin" (DCO) is listed in the file
+	Documentation/SubmittingPatches.
 
 6.	Make sure you have the right to send any changes you make. If you
 	do changes at work you may find your employer owns the patch
-

Previous thread: Linux Foundation Technical Advisory Board Elections by James Bottomley on Wednesday, August 22, 2007 - 8:22 am. (62 messages)

Next thread: Patch for Apani Nortel VPN Client to build against kernel 2.6.22 help/review by Fortier,Vincent [Montreal] on Wednesday, August 22, 2007 - 8:38 am. (3 messages)