Difference between revisions of "How to submit patches"
m (add 'translate' tags) |
(Marked this version for translation) |
||
| Line 2: | Line 2: | ||
<translate> | <translate> | ||
| + | <!--T:1--> | ||
* [[Kernel patches]] | * [[Kernel patches]] | ||
* [[Userspace patches]] | * [[Userspace patches]] | ||
* [[Best practices for development of EZ templates]] | * [[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, | ||
| Line 13: | Line 15: | ||
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 == | + | == External links == <!--T:4--> |
| + | <!--T:5--> | ||
* [[OpenVZ_infrastructure#Code|OpenVZ source code]] | * [[OpenVZ_infrastructure#Code|OpenVZ source code]] | ||
</translate> | </translate> | ||
Latest revision as of 22:37, 25 December 2015
This article is for Virtuozzo 7 only.<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>
