427
edits
Changes
Jump to navigation
Jump to search
no edit summary
Line 1:
Line 1:
===================================
− +-------------------------
------------------------
-----------------
-----------------
---------------------------
−
−From: Random J Developer <random at developer.example.org>
−Subject: [PATCH] Short patch description
−
−Long patch description (could be skipped if patch
−is trivial enough)
−
+
+---------------
-----------------
---
− With best regards,
− CRIU-team
How to submit patches into the CRIU
How to submit patches into the CRIU
−=Obtaining the source code=
−Obtaining the source code
−The CRIU sources are tracked by Git SCM at http://git.criu.org
The CRIU sources are tracked by Git SCM at http://git.criu.org
Line 15:
Line 12:
−Changing the source code
+=Changing the source code=
−When you change the source code keep in mind -- we prefer tabs and
When you change the source code keep in mind -- we prefer tabs and
Line 25:
Line 21:
−Producing a patch
+=Producing a patch=
−There are at least two ways to make it right.
There are at least two ways to make it right.
Line 42:
Line 37:
−Signing your work
+=Signing your work=
−To improve tracking of who did what we've introduced a "sign-off" procedure
To improve tracking of who did what we've introduced a "sign-off" procedure
Line 87:
Line 81:
−An example of patch message
+=An example of patch message=
−Signed-off-by: Random J Developer <random at developer.example.org>
+ From: Random J Developer <random at developer.example.org>
−---
+ Subject: [PATCH] Short patch description
−Patch body here
+ Long patch description (could be skipped if patch
+ is trivial enough)
+ Signed-off-by: Random J Developer <random at developer.example.org>
+ ---
+ Patch body here
−Mailing patches
+=Mailing patches
−The patches should be sent to CRIU development mailing list
The patches should be sent to CRIU development mailing list
Line 111:
Line 103:
−Wait for response
+=Wait for response=
−Be patient. Most CRIU developers are pretty busy people so if
Be patient. Most CRIU developers are pretty busy people so if
Line 118:
Line 109:
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 /dev/null.
−