|
|
| (34 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| __TOC__
| | The instructions previously available on this page have been superseded. See [https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/git/README.md here]. |
| | |
| 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/gitweb.
| |
| | |
| ==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
| |
| | |
| For ParaViewData the URLs are
| |
| | |
| git://paraview.org/ParaViewData.git
| |
| http://paraview.org/ParaViewData.git
| |
| git@paraview.org:ParaViewData.git
| |
| | |
| See the [[VTK/Git | VTK]] Git documentation for further details.
| |
| | |
| ==Branches==
| |
| | |
| At the time of this writing the repository has the following branches:
| |
| | |
| * '''master''': Development (default)
| |
| * '''release''': Release preparation branch (prior to switching to a brancy workflow; may go away later)
| |
| * '''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==
| |
| | |
| ParaView references a few other projects as ''submodules''. They can be obtained using the [http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html 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 <code>git://vtk.org/VTK.git</code> 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 '<code>VTK</code>'.
| |
| Repository URLs:
| |
| | |
| git://vtk.org/VTK.git
| |
| http://vtk.org/VTK.git
| |
| git@vtk.org:VTK.git
| |
| | |
| ===IceT===
| |
| | |
| ParaView references IceT as a ''submodule'' called '<code>IceT</code>' at path '<code>Utilities/IceT</code>'.
| |
| Repository URLs:
| |
| | |
| git://paraview.org/IceT.git
| |
| http://paraview.org/IceT.git
| |
| git@paraview:IceT.git
| |
|
| |
| git://public.kitware.com/IceT.git
| |
| http://public.kitware.com/IceT.git
| |
| git@public.kitware.com:IceT.git
| |
| | |
| ===Xdmf===
| |
| | |
| ParaView references Xdmf as a ''submodule'' called '<code>Xdmf</code>' at path '<code>Utilities/Xdmf2</code>'.
| |
| Repository URLs:
| |
| | |
| git://paraview.org/Xdmf.git
| |
| http://paraview.org/Xdmf.git
| |
| git@paraview:Xdmf.git
| |
|
| |
| git://public.kitware.com/Xdmf.git
| |
| http://public.kitware.com/Xdmf.git
| |
| git@public.kitware.com:Xdmf.git
| |
