ParaView/Git: Difference between revisions
From KitwarePublic
< ParaView
Jump to navigationJump to search
Line 72: | Line 72: | ||
|push (ssh) | |push (ssh) | ||
|<code>git@paraview.org:PVVTK.git</code> | |<code>git@paraview.org:PVVTK.git</code> | ||
|- | |||
|rowspan=3|<code>stage/ParaView.git</code> | |||
|rowspan=3|ParaView Super-Build | |||
|fetch (git) | |||
|<code>git://paraview.org/ParaViewSuperbuild.git</code> | |||
|- | |||
|fetch (http) | |||
|<code>http://paraview.org/ParaViewSuperbuild.git</code> | |||
|- | |||
|push (ssh) | |||
|<code>git@paraview.org:ParaViewSuperbuild.git</code> | |||
|} | |} | ||
Revision as of 06:10, 17 August 2012
Introduction
ParaView version tracking and development is hosted by Git. Please select a task for further instructions:
Main Tasks: |
|
|
|
|
Other Tasks: |
|
The remainder of this page provides reference information and links. It is not intended to provide instructions.
Repositories
One may browse the repositories online using the Gitweb interface at http://paraview.org/gitweb.
Repository | Purpose | Access | URL |
---|---|---|---|
ParaView.git
|
ParaView | clone (git) | git://paraview.org/ParaView.git
|
clone (http) | http://paraview.org/ParaView.git
| ||
push (ssh) | git@paraview.org:ParaView.git
| ||
stage/ParaView.git
|
ParaView Topic Stage | fetch (git) | git://paraview.org/stage/ParaView.git
|
fetch (http) | http://paraview.org/stage/ParaView.git
| ||
push (ssh) | git@paraview.org:stage/ParaView.git
| ||
PVVTK.git
|
PVVTK Topic Stage | fetch (git) | git://paraview.org/PVVTK.git
|
fetch (http) | http://paraview.org/PVVTK.git
| ||
push (ssh) | git@paraview.org:PVVTK.git
| ||
stage/ParaView.git
|
ParaView Super-Build | fetch (git) | git://paraview.org/ParaViewSuperbuild.git
|
fetch (http) | http://paraview.org/ParaViewSuperbuild.git
| ||
push (ssh) | git@paraview.org:ParaViewSuperbuild.git
|
Branches
At the time of this writing the ParaView.git
repository has the following branches:
- release: Release maintenance; bug fixes only
- master: Release preparation; starting point for new features (default)
- next: Development; new features published here first
- nightly-master: Follows master, updated at 01:00 UTC
- nightly-next: Follows next, updated at 01:00 UTC
- hooks: Local commit hooks (place in .git/hooks)
Release branches converted from CVS have been artificially merged into master. Actual releases have tags named by the release version number.