Difference between revisions of "How to submit patches"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(remove content as we plan to create separate articles)
(Marked this version for translation)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{Virtuozzo}}
 +
 +
<translate>
 +
<!--T:1-->
 
* [[Kernel patches]]
 
* [[Kernel patches]]
 
* [[Userspace patches]]
 
* [[Userspace patches]]
 +
* [[Best practices for development of EZ templates]]
  
== Wait for response ==
+
== Wait for response == <!--T:2-->
  
 +
<!--T:3-->
 
Be patient. Most OpenVZ developers are pretty busy people so if
 
Be patient. Most OpenVZ 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>.
 +
 +
== External links == <!--T:4-->
 +
 +
<!--T:5-->
 +
* [[OpenVZ_infrastructure#Code|OpenVZ source code]]
 +
</translate>
  
 
[[Category:Development]]
 
[[Category:Development]]
 +
[[Category:Contributions]]
 +
[[Category:Virtuozzo]]

Latest revision as of 22:37, 25 December 2015

<translate>

Wait for response[edit]

Be patient. Most OpenVZ developers are pretty busy people so if 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. But definitely the patches will not go to /dev/null.

External links[edit]

</translate>