]>
Commit | Line | Data |
---|---|---|
1f81f05a TT |
1 | |
2 | Like the Linux kernel, submitted e2fsprogs patches now require the | |
3 | following "sign-off" procedure: | |
4 | ||
5 | The sign-off is a simple line at the end of the explanation for the | |
6 | patch, which certifies that you wrote it or otherwise have the right to | |
7 | pass it on as a open-source patch. The rules are pretty simple: if you | |
8 | can certify the below: | |
9 | ||
10 | Developer's Certificate of Origin 1.1 | |
11 | ||
12 | By making a contribution to this project, I certify that: | |
13 | ||
14 | (a) The contribution was created in whole or in part by me and I | |
15 | have the right to submit it under the open source license | |
16 | indicated in the file; or | |
17 | ||
18 | (b) The contribution is based upon previous work that, to the best | |
19 | of my knowledge, is covered under an appropriate open source | |
20 | license and I have the right under that license to submit that | |
21 | work with modifications, whether created in whole or in part | |
22 | by me, under the same open source license (unless I am | |
23 | permitted to submit under a different license), as indicated | |
24 | in the file; or | |
25 | ||
26 | (c) The contribution was provided directly to me by some other | |
27 | person who certified (a), (b) or (c) and I have not modified | |
28 | it. | |
29 | ||
30 | (d) I understand and agree that this project and the contribution | |
31 | are public and that a record of the contribution (including all | |
32 | personal information I submit with it, including my sign-off) is | |
33 | maintained indefinitely and may be redistributed consistent with | |
34 | this project or the open source license(s) involved. | |
35 | ||
36 | then you just add a line saying | |
37 | ||
38 | Signed-off-by: Random J Developer <random@developer.example.org> | |
39 |