1,072
edits
Changes
Jump to navigation
Jump to search
do NOT use first-level headings. oh please.
Line 1:
Line 1:
−
=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 9:
Line 9:
git clone git://git.criu.org/crtools.git
git clone git://git.criu.org/crtools.git
−=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 17:
Line 17:
to look similar.
to look similar.
−=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 32:
Line 32:
Use <code>diff -up</code> or <code>diff -uprN</code> to create patches.
Use <code>diff -up</code> or <code>diff -uprN</code> to create patches.
−=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 75:
Line 75:
it possible)
it possible)
−=An example of patch message=
+== An example of patch message ==
From: Random J Developer <random at developer.example.org>
From: Random J Developer <random at developer.example.org>
Line 87:
Line 87:
Patch body here
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 95:
Line 95:
your patch (line wrapping and so on).
your patch (line wrapping and so on).
−=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