Jump to: navigation, search

How to submit patches

193 bytes added, 00:23, 22 March 2017
Continuous integration: expand, add links. Fix examples formatting
To clone CRIU repo and switch to the proper branch, run:
<sourcepre><nowiki> git clone criu cd criu git checkout criu-dev</sourcenowiki></pre>
== Compile ==
To compile CRIU, run:
<source> make</source>
This should create the <code>./criu/criu</code> executable.
can certify the below:
<div class="toccolours mw-collapsible mw-collapsed" style="width: 64em46em;">
'''Developer's Certificate of Origin 1.1'''
<div class="mw-collapsible-content">
<code>git commit --amend -s</code>.
<div class="toccolours mw-collapsible mw-collapsed" style="width: 64em46em;">
'''Example patch message'''
<div class="mw-collapsible-content">
sometimes a patch may fly around a week before it gets reviewed.
== Continuous Integration integration == ''Main article: [[Continuous integration]]'' CRIU tests are run for each seriessent to the mailing list. If you get a message from our patchwork that patches haven't failed to pass the tests, you have to investigate what is wrong.  We also recommend you to use [[Continuous integration#Enable Travis CI for your repo|enable Travis CI for your repo]] to check patches in your git branch, before sending them into to the mailing list.

Navigation menu