Difference between revisions of "ParaView/Git"

From KitwarePublic
Jump to: navigation, search
(Official Repository)
(Repositories)
(35 intermediate revisions by 6 users not shown)
Line 1: Line 1:
__TOC__
+
==Introduction==
  
 
ParaView version tracking and development is hosted by [http://git-scm.com Git].
 
ParaView version tracking and development is hosted by [http://git-scm.com Git].
 +
Please select a task for further instructions:
  
=Official Repository=
+
{|border="0"
 +
|-
 +
|width=70%|
 +
Main Tasks:
 +
|-
 +
|
 +
:*<span style="font-size: 1.5em">[[Git/Download|Install Git]]</span> - Git 1.6.5 or greater is preferred
 +
|-
 +
|
 +
:*<span style="font-size: 1.5em">[[ParaView/Git/Download|Download ParaView]] - Users start here</span>
 +
|-
 +
|
 +
:*<span style="font-size: 1.5em">[[ParaView/Git/Develop|Develop ParaView]] - Contributors start here</span>
 +
|-
 +
|
 +
:*<span style="font-size: 1.5em">[[ParaView/Git/Maintain|Maintain ParaView]] - Maintainers start here</span>
 +
|-
 +
|
 +
Other Tasks:
 +
|-
 +
|
 +
:*<span style="font-size: 1.5em">[[Git/Resources|Learn Git]]</span> - Third-party documentation
 +
|}
  
One may browse the repository online using the [http://git.wiki.kernel.org/index.php/Gitweb Gitweb] interface at http://paraview.org/ParaView.git.
+
''The remainder of this page provides reference information and links. It is not intended to provide instructions.''
  
==Cloning==
+
==Repositories==
  
The clone URLs for the repository are
+
One may browse the repositories online using the [http://git.wiki.kernel.org/index.php/Gitweb Gitweb] interface at http://paraview.org/gitweb.
  
git://paraview.org/ParaView.git
+
{|border="1" cellspacing="0" cellpadding="3"
http://paraview.org/ParaView.git
+
!Repository
 
+
!Purpose
The push URL for the repository is
+
!Access
 
+
!URL
git@paraview.org:ParaView.git
+
|-
 
+
|rowspan=3|<code>ParaView.git</code>
''Pushes to the ParaView.git repository have been disabled during the final transition to Git.''
+
|rowspan=3|ParaView
 
+
|clone (git)
For ParaViewData the URLs are
+
|<code>git://paraview.org/ParaView.git</code>
 
+
|-
git://paraview.org/ParaViewData.git
+
|clone (http)
http://paraview.org/ParaViewData.git
+
|<code>http://paraview.org/ParaView.git</code>
git@paraview.org:ParaViewData.git
+
|-
 
+
|push (ssh)
See the [[VTK/Git | VTK]] Git documentation for further details.
+
|<code>git@paraview.org:ParaView.git</code>
 +
|-
 +
|rowspan=3|<code>stage/ParaView.git</code>
 +
|rowspan=3|ParaView Topic Stage
 +
|fetch (git)
 +
|<code>git://paraview.org/stage/ParaView.git</code>
 +
|-
 +
|fetch (http)
 +
|<code>http://paraview.org/stage/ParaView.git</code>
 +
|-
 +
|push (ssh)
 +
|<code>git@paraview.org:stage/ParaView.git</code>
 +
|-
 +
|rowspan=3|<code>PVVTK.git</code>
 +
|rowspan=3|PVVTK Topic Stage
 +
|fetch (git)
 +
|<code>git://paraview.org/PVVTK.git</code>
 +
|-
 +
|fetch (http)
 +
|<code>http://paraview.org/PVVTK.git</code>
 +
|-
 +
|push (ssh)
 +
|<code>git@paraview.org:PVVTK.git</code>
 +
|-
 +
|rowspan=3|<code>ParaViewSuperbuild.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>
 +
|}
  
 
==Branches==
 
==Branches==
  
At the time of this writing the repository has the following branches:
+
At the time of this writing the <code>ParaView.git</code> repository has the following branches:
 
+
* '''master''': Development (default)
+
* '''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>'.
+
* '''release''': Release maintenance; bug fixes only
Repository URLs:
+
* '''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 ([[Git/Hooks#Local|place]] in .git/hooks)
  
git://paraview.org/Xdmf.git
+
Release branches converted from CVS have been artificially merged into master.
http://paraview.org/Xdmf.git
+
Actual releases have tags named by the release version number.
git@paraview:Xdmf.git
+
+
git://public.kitware.com/Xdmf.git
+
http://public.kitware.com/Xdmf.git
+
git@public.kitware.com:Xdmf.git
+

Revision as of 02:11, 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
ParaViewSuperbuild.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.