Difference between revisions of "How to submit patches"
(added link to source code) |
|||
| Line 8: | Line 8: | ||
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 == | ||
| + | |||
| + | * [[OpenVZ_infrastructure#Code|OpenVZ source code]] | ||
[[Category:Development]] | [[Category:Development]] | ||
[[Category: Contributions]] | [[Category: Contributions]] | ||
Revision as of 16:38, 2 June 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.
