Editing OpenVZ infrastructure
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 6: | Line 6: | ||
We have a single place for all OpenVZ source code - [https://src.openvz.org/ src.openvz.org]. It contains two projects: | We have a single place for all OpenVZ source code - [https://src.openvz.org/ src.openvz.org]. It contains two projects: | ||
− | with [https://src.openvz.org/projects/OVZL legacy OpenVZ components] and [https://src.openvz.org/projects/OVZ Virtuozzo components]. We use [https://git-scm.herokuapp.com/ GIT SCM] to track changes in source code. Each OpenVZ component is a separate GIT repository. All patches should be reviewed before committing to repository. Please read article [[How to submit patches]] before sending patch. Each repository on src.openvz.org has a mirror on [https://github.com/OpenVZ Github account OpenVZ] for your convenience. | + | with [https://src.openvz.org/projects/OVZL legacy OpenVZ components] and [https://src.openvz.org/projects/OVZ Virtuozzo components]. We use [https://git-scm.herokuapp.com/ GIT SCM] to track changes in source code. Each OpenVZ component is a separate GIT repository. All patches should be reviewed before committing to repository. Please read article [[How to submit patches]] before sending patch. Each repository on src.openvz.org has a mirror on [https://github.com/OpenVZ Github account OpenVZ] for your convenience. Also see how to monitor [[User:Kir/Latest_commits|latest commits]]. |
== Bugs == | == Bugs == |