From 7d71be37194df05c349157a2161c7534feaf86a4 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Fri, 24 Jan 2014 15:06:11 -0800 Subject: [PATCH] Documentation/SubmittingPatches: Reference external DCO The new developer-certificate-of-origin text is copied directly from developercertificate.org [1] into a stand-alone file to avoid confusion with the separately-licensed supporting text in SubmittingPatches (following the example of stand-alone license files like COPYING). SubmittingPatches now references that file when explaining the significance of Signed-off-by tags. My changes to SubmittingPatches are licensed under both the Creative Commons CC0 1.0 Universal license (see the `license` branch for full text) and the GPLv2-linux (see the `copying` branch for full text), as are my previous contributions to SubmittingPatches. Pick whichever one works best for you. [1]: http://developercertificate.org/ Signed-off-by: W. Trevor King --- Documentation/SubmittingPatches | 32 +++----------------------------- 1 file changed, 3 insertions(+), 29 deletions(-) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 3405598..0da865b 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -2,35 +2,9 @@ To improve tracking of who did what, we use the "sign-off" procedure introduced by the Linux kernel. The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right to pass it on as an open-source patch. -The rules are pretty simple: if you can certify the below: - - 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. - -then you just add a line saying +The rules are pretty simple: if you can certify the Developer's +Certificate of Origin 1.1 (see the developer-certificate-of-origin +file), then you just add a line saying Signed-off-by: Random J Developer -- 2.26.2