Difference between revisions of "How to submit patches"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(add link to Best practices)
m (moved practices on top)
Line 3: Line 3:
 
* [[Kernel patches]]
 
* [[Kernel patches]]
 
* [[Userspace patches]]
 
* [[Userspace patches]]
 +
* [[Best practices for development of EZ templates]]
  
 
== Wait for response ==
 
== Wait for response ==
Line 14: Line 15:
  
 
* [[OpenVZ_infrastructure#Code|OpenVZ source code]]
 
* [[OpenVZ_infrastructure#Code|OpenVZ source code]]
* [[Best practices for development of EZ templates]]
 
  
 
[[Category:Development]]
 
[[Category:Development]]
 
[[Category:Contributions]]
 
[[Category:Contributions]]
 
[[Category:Virtuozzo]]
 
[[Category:Virtuozzo]]

Revision as of 17:01, 11 September 2015

Wait for response

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