Open main menu

OpenVZ Virtuozzo Containers Wiki β

Difference between revisions of "Userspace patches"

(added category)
(Marked this version for translation)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{Virtuozzo}}
 +
 +
<translate>
 +
<!--T:1-->
 
We are waiting for contributions to userspace utilities from OpenVZ community.
 
We are waiting for contributions to userspace utilities from OpenVZ community.
We will describe process of contribution soon.
+
 
Now please follow [https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow this guide].
+
<!--T:2-->
 +
This document describes how to contribute your patches to the OpenVZ userspace.
 +
 
 +
== Source code == <!--T:3-->
 +
 
 +
<!--T:4-->
 +
OpenVZ source code is available from GIT repository at
 +
 
 +
<!--T:5-->
 +
https://src.openvz.org/projects/OVZ
 +
 
 +
<!--T:6-->
 +
To clone, use
 +
 +
git clone https://src.openvz.org/scm/ovz/<project>.git
 +
 
 +
<!--T:7-->
 +
For example:
 +
 
 +
<!--T:8-->
 +
git clone https://src.openvz.org/scm/ovz/prlctl.git
 +
 
 +
 
 +
 
 +
== Preparing patches == <!--T:9-->
 +
 
 +
<!--T:10-->
 +
For new code please follow:
 +
* C++ language - [[C++ Code Style Guide]]
 +
* C language - [https://www.kernel.org/doc/Documentation/CodingStyle Linux kernel code style]
 +
* Python language - [https://www.python.org/dev/peps/pep-0008/ Python code style]
 +
 
 +
<!--T:11-->
 +
For existing code patches, please follow a style which is used for code around.   
 +
 
 +
== Send pull request == <!--T:12-->
 +
 
 +
<!--T:13-->
 +
For contributions, please register at [https://src.openvz.org our Stash site] and follow [https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow "forking" workflow].
 +
 
 +
 
 +
== See also == <!--T:14-->
 +
 
 +
<!--T:15-->
 +
* [[Contribute]]
 +
* [[C++ Code Style Guide]]
 +
* [[Static code analysis]]
 +
* [[Wishlist]]
 +
* [[QA|OpenVZ Testing]]
 +
</translate>
  
 
[[Category: Contributions]]
 
[[Category: Contributions]]
 +
[[Category:Virtuozzo]]

Latest revision as of 08:37, 26 December 2015

<translate> We are waiting for contributions to userspace utilities from OpenVZ community.

This document describes how to contribute your patches to the OpenVZ userspace.

Contents

Source codeEdit

OpenVZ source code is available from GIT repository at

https://src.openvz.org/projects/OVZ

To clone, use

git clone https://src.openvz.org/scm/ovz/<project>.git

For example:

git clone https://src.openvz.org/scm/ovz/prlctl.git


Preparing patchesEdit

For new code please follow:

For existing code patches, please follow a style which is used for code around.

Send pull requestEdit

For contributions, please register at our Stash site and follow "forking" workflow.


See alsoEdit