Changes
Jump to navigation
Jump to search
← Older edit
Newer edit →
How to submit patches
(edit)
Revision as of 10:55, 27 January 2013
3 bytes removed
,
10:55, 27 January 2013
no edit summary
Line 13:
Line 13:
=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
indentations to be 8 characters width.
indentations to be 8 characters width.
−
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.
Line 100:
Line 100:
Be patient. Most CRIU developers are pretty busy people so if
Be patient. Most CRIU developers are pretty busy people so if
−
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 <code>/dev/null</code>.
But definitely the patches will not go to <code>/dev/null</code>.
Cyrillos
Bureaucrats
,
Administrators
433
edits
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Request account
Log in
Namespaces
Page
Discussion
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help
Tools
Special pages
Printable version
News
Twitter
YouTube
External resources
Github / source code
Issues / bugs
Mr. Jenkins
Open Hub
OpenVZ