433
edits
Changes
Jump to navigation
Jump to search
no edit summary
Line 10:
Line 10:
You might need to read documentation on Git SCM how to prepare patch+ for mail submission. Take a look on http://book.git-scm.com/ and/or+ http://git-scm.com/documentation for details. It should not be hard+ at all.+ Use "diff -up" or "diff -uprN" to create patches.+
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.+
git clone git://git.criu.org/crtools.git
git clone git://git.criu.org/crtools.git
−=Changing the source code=
=Changing the source code=
Line 19:
Line 18:
Other "rules" could be learned from the source code -- just make your code
Other "rules" could be learned from the source code -- just make your code
to look similar.
to look similar.
−=Producing a patch=
=Producing a patch=
Line 27:
Line 25:
1) git format-patch
1) git format-patch
−You might need to read documentation on Git SCM how to prepare patch
−for mail submission. Take a look on http://book.git-scm.com/ and/or
−http://git-scm.com/documentation for details. It should not be hard
−at all.
2) Use "diff -up"
2) Use "diff -up"
−Use <code>diff -up</code> or <code>diff -uprN</code> to create patches.
−=Signing your work=
=Signing your work=
Line 47:
Line 44:
can certify the below:
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
then you just add a line saying
Line 91:
Line 88:
---
---
Patch body here
Patch body here
−=Mailing patches=
=Mailing patches=
Line 106:
Line 102:
there is no immediate response on your patch -- don't be surprised,
there is no immediate response on your patch -- don't be surprised,
sometimes a patch may fly around a week(s) before it get reviewed.
sometimes a patch may fly around a week(s) before it get reviewed.
−But definitely the patches will not go to /dev/null.
+But definitely the patches will not go to <code>/dev/null</code>.