ParaView/Git: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
ParaView version tracking and development is hosted by [http://git-scm.com Git]. | |||
=Official Repository= | |||
One may browse the repository online using the [http://git.wiki.kernel.org/index.php/Gitweb Gitweb] interface at http://paraview.org/ParaView.git. | One may browse the repository online using the [http://git.wiki.kernel.org/index.php/Gitweb Gitweb] interface at http://paraview.org/ParaView.git. | ||
==Cloning== | ==Cloning== | ||
| Line 23: | Line 18: | ||
git@paraview.org:ParaView.git | git@paraview.org:ParaView.git | ||
''Pushes to the | ''Pushes to the ParaView.git repository have been disabled during the final transition to Git.'' | ||
See the [[VTK/Git | VTK]] Git documentation for further details. | See the [[VTK/Git | VTK]] Git documentation for further details. | ||
| Line 33: | Line 28: | ||
* '''master''': Development (default) | * '''master''': Development (default) | ||
* '''hooks''': Local commit hooks ([[VTK/Git#Hooks|place]] in .git/hooks) | * '''hooks''': Local commit hooks ([[VTK/Git#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. | |||
==Submodules== | ==Submodules== | ||
| Line 63: | Line 60: | ||
===Xdmf=== | ===Xdmf=== | ||
ParaView references Xdmf as a ''submodule'' called '<code> | ParaView references Xdmf as a ''submodule'' called '<code>Xdmf</code>' at path '<code>Utilities/Xdmf2</code>'. | ||
Revision as of 18:01, 18 April 2010
ParaView version tracking and development is hosted by Git.
Official Repository
One may browse the repository online using the Gitweb interface at http://paraview.org/ParaView.git.
Cloning
The clone URLs for the repository are
git://paraview.org/ParaView.git http://paraview.org/ParaView.git
The push URL for the repository is
git@paraview.org:ParaView.git
Pushes to the ParaView.git repository have been disabled during the final transition to Git.
See the VTK Git documentation for further details.
Branches
At the time of this writing the repository has the following branches:
- master: Development (default)
- 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.
Submodules
ParaView references a few other projects as submodules. They can be obtained using the git submodule command. First use the 'init' subcommand to register the submodules:
$ git submodule init
This configures the submodules to fetch from their default URLs, such as git://vtk.org/VTK.git for VTK.
Next one may optionally configure a different URL, perhaps to use the http protocol:
$ git config submodule.VTK.url http://vtk.org/VTK.git
(and similarly for other submodules if necessary). Finally, use the 'update' subcommand to get the submodules:
$ git submodule update
Whenever you update your work tree to some revision of ParaView then 'git status' may report that the submodule directories are modified. This is because commands like 'git checkout' do not automatically update submodules. Use 'git submodule update' at any time to ensure that the submodule directories are updated to the versions referenced by the parent project.
VTK
ParaView references VTK as a submodule called 'VTK'.
IceT
ParaView references IceT as a submodule called 'IceT' at path 'Utilities/IceT'.
Xdmf
ParaView references Xdmf as a submodule called 'Xdmf' at path 'Utilities/Xdmf2'.
