Editing Userspace patches

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
{{Virtuozzo}}
 
{{Virtuozzo}}
 +
{{Stub}}
  
<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 == <!--T:3-->
+
== Source code ==
  
<!--T:4-->
 
 
OpenVZ source code is available from GIT repository at
 
OpenVZ source code is available from GIT repository at
  
  <!--T:5-->
+
  https://src.openvz.org/projects/OVZ
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:
  
  <!--T:8-->
+
  git clone https://src.openvz.org/scm/ovz/prlctl.git
git clone https://src.openvz.org/scm/ovz/prlctl.git
 
  
  
  
== Preparing patches == <!--T:9-->
+
== Preparing patches ==
  
<!--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 37: Line 29:
 
* 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 == <!--T:12-->
+
== Send pull request ==
  
<!--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 == <!--T:14-->
+
== See also ==
  
<!--T:15-->
 
 
* [[Contribute]]
 
* [[Contribute]]
 
* [[C++ Code Style Guide]]
 
* [[C++ Code Style Guide]]
Line 54: Line 43:
 
* [[Wishlist]]
 
* [[Wishlist]]
 
* [[QA|OpenVZ Testing]]
 
* [[QA|OpenVZ Testing]]
</translate>
 
  
 
[[Category: Contributions]]
 
[[Category: Contributions]]
 
[[Category:Virtuozzo]]
 
[[Category:Virtuozzo]]

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: