Difference between revisions of "ParaView/Git"

From KitwarePublic
Jump to: navigation, search
(Created page with 'ParaView version tracking and development will be hosted by [http://git-scm.com Git]. We have published an ''experimental'' repository on paraview.org. '''WE REQUEST THAT NO ONE…')
 
(Repositories)
(44 intermediate revisions by 6 users not shown)
Line 1: Line 1:
ParaView version tracking and development will be hosted by [http://git-scm.com Git].
+
==Introduction==
  
We have published an ''experimental'' repository on paraview.org. '''WE REQUEST THAT NO ONE PUBLISH A CLONE OF THIS REPOSITORY AT AN ONLINE HOSTING SITE'''. This may or may not be the final version of history after conversion from CVS. It may be removed or rewritten at any time. We prefer to not have multiple incompatible histories out there. The final conversion will be available soon, at which point we may all begin sharing changes!
+
ParaView version tracking and development is hosted by [http://git-scm.com Git].
 +
Please select a task for further instructions:
  
One may browse the repository online using the [http://git.wiki.kernel.org/index.php/Gitweb Gitweb] interface at http://paraview.org/paraview-tmp.git.
+
{|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
 +
|}
  
At the time of this writing the repository does not have branches.
+
''The remainder of this page provides reference information and links.  It is not intended to provide instructions.''
Conversion of branches and tags from CVS will be completed later and added.
+
  
The clone URLs for the repository are
+
==Repositories==
  
git://paraview.org/paraview-tmp.git
+
One may browse the repositories online using the [http://git.wiki.kernel.org/index.php/Gitweb Gitweb] interface at http://paraview.org/gitweb.
http://paraview.org/paraview-tmp.git
+
  
The push URL for the repository is
+
{|border="1" cellspacing="0" cellpadding="3"
 +
!Repository
 +
!Purpose
 +
!Access
 +
!URL
 +
|-
 +
|rowspan=3|<code>ParaView.git</code>
 +
|rowspan=3|ParaView
 +
|clone (git)
 +
|<code>git://paraview.org/ParaView.git</code>
 +
|-
 +
|clone (http)
 +
|<code>http://paraview.org/ParaView.git</code>
 +
|-
 +
|push (ssh)
 +
|<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>
 +
|}
  
git@paraview.org:paraview-tmp.git
+
==Branches==
  
See the [[VTK/Git | VTK]] Git documentation for further details.
+
At the time of this writing the <code>ParaView.git</code> 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 ([[Git/Hooks#Local|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.

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.