Hi David, On 01/09/18 03:21, David Gibson wrote: > On Mon, Jan 08, 2018 at 02:36:45PM +0100, Julia Lawall wrote: >> Based on the following patch by Frank Rowand (no changes): >> >> >> https://www.mail-archive.com/devicetree-compiler@xxxxxxxxxxxxxxx/msg00378.html > > If there are no changes, then it should definitely have Frank's S-o-b. > >> >> Signed-off-by: Julia Lawall <Julia.Lawall@xxxxxxx> >> --- < snip > In the context of the S-o-b questions, I was referencing the Linux kernel documentation for the meaning of S-o-b. I realized that I should check that the same (or similar) definitions existed in the dtc project, but have not found that definition. Should that definition be added to file README.license? I think the appropriate portion of the Linux kernel file Documentation/process/submitting-patches.rst (which to the best of my understanding is GPL v2) is a portion of section "11) Sign your work - the Developer's Certificate of Origin": 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:: Signed-off-by: Random J Developer <random@xxxxxxxxxxxxxxxxxxxxx> using your real name (sorry, no pseudonyms or anonymous contributions.) -- To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
