Difference between revisions of "Userspace patches"
(Marked this version for translation) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Virtuozzo}} | {{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. | ||
| + | <!--T:2--> | ||
This document describes how to contribute your patches to the OpenVZ userspace. | This document describes how to contribute your patches to the OpenVZ userspace. | ||
| − | == Source code == | + | == Source code == <!--T:3--> |
| + | <!--T:4--> | ||
OpenVZ source code is available from GIT repository at | OpenVZ source code is available from GIT repository at | ||
| − | https://src.openvz.org/projects/OVZ | + | <!--T:5--> |
| + | https://src.openvz.org/projects/OVZ | ||
| + | <!--T:6--> | ||
To clone, use | To clone, use | ||
git clone https://src.openvz.org/scm/ovz/<project>.git | git clone https://src.openvz.org/scm/ovz/<project>.git | ||
| + | <!--T:7--> | ||
For example: | For example: | ||
| − | git clone https://src.openvz.org/scm/ovz/prlctl.git | + | <!--T:8--> |
| + | git clone https://src.openvz.org/scm/ovz/prlctl.git | ||
| − | == Preparing patches == | + | == Preparing patches == <!--T:9--> |
| + | <!--T:10--> | ||
For new code please follow: | For new code please follow: | ||
* C++ language - [[C++ Code Style Guide]] | * C++ language - [[C++ Code Style Guide]] | ||
| Line 29: | Line 37: | ||
* Python language - [https://www.python.org/dev/peps/pep-0008/ Python 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. | For existing code patches, please follow a style which is used for code around. | ||
| − | == Send pull request == | + | == 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]. | 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 == | + | == See also == <!--T:14--> |
| + | <!--T:15--> | ||
* [[Contribute]] | * [[Contribute]] | ||
* [[C++ Code Style Guide]] | * [[C++ Code Style Guide]] | ||
| Line 43: | Line 54: | ||
* [[Wishlist]] | * [[Wishlist]] | ||
* [[QA|OpenVZ Testing]] | * [[QA|OpenVZ Testing]] | ||
| + | </translate> | ||
[[Category: Contributions]] | [[Category: Contributions]] | ||
[[Category:Virtuozzo]] | [[Category:Virtuozzo]] | ||
Latest revision as of 08:37, 26 December 2015
This article is for Virtuozzo 7 only.<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:
- C++ language - C++ Code Style Guide
- C language - Linux kernel code style
- Python language - Python code style
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.