VTK/Git: Difference between revisions
| Line 43: | Line 43: | ||
The <code>--global</code> option stores the configuration settings in <code>~/.gitconfig</code> in your home directory so that they apply to all repositories. | The <code>--global</code> option stores the configuration settings in <code>~/.gitconfig</code> in your home directory so that they apply to all repositories. | ||
=Publishing= | |||
Authorized developers may publish work | Authorized developers may publish work directly to <code>public.kitware.com/vtk-tmp.git</code> using Git's SSH protocol. | ||
==Authentication== | |||
All publishers share the <code>git@public.kitware.com</code> account but each uses a unique ssh key for authentication. | |||
To request access, fill out the [https://www.kitware.com/Admin/SendPassword.cgi Kitware Password] form. | |||
Include your ssh public key and a reference to someone our administrators may contact to verify your privileges. | |||
Note that ''we may not grant all contributors push access'' to the <code>public.kitware.com</code> repository. | |||
The distributed nature of Git allows contributors to retain authorship credit even if they do not publish changes directly. | |||
'''After the final conversion to Git''' is finished we will consider pull requests from online Git hosting sites. | |||
==Pushing== | |||
Git automatically configures a new clone to refer to its origin through a [http://www.kernel.org/pub/software/scm/git/docs/git-remote.html remote] called <code>origin</code>. | Git automatically configures a new clone to refer to its origin through a [http://www.kernel.org/pub/software/scm/git/docs/git-remote.html remote] called <code>origin</code>. | ||
| Line 57: | Line 69: | ||
(Note that 'pushurl' requires Git >= 1.6.4. Use just 'url' for Git < 1.6.4.) | (Note that 'pushurl' requires Git >= 1.6.4. Use just 'url' for Git < 1.6.4.) | ||
Once your push URL is configured and your key is installed for <code>git@public.kitware.com</code> then you can try pushing changes. | Once your push URL is configured and your key is installed for <code>git@public.kitware.com</code> then you can try pushing changes. | ||
Revision as of 14:59, 26 March 2010
VTK version tracking and development will be hosted by Git.
Experimental Repository
We have published an experimental repository on public.kitware.com. 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!
One may browse the repository online using the Gitweb interface at http://public.kitware.com/vtk-tmp.git/.
At the time of this writing the repository does not have branches and tags older than VTK 5.0. Conversion of older branches and tags from CVS will be completed later and added.
Cloning
One may clone the repository using git clone through the native git protocol:
$ git clone git://public.kitware.com/vtk-tmp.git VTK
or through the (less efficient) http protocol:
$ git clone http://public.kitware.com/vtk-tmp.git VTK
All further commands work inside the local copy of the repository created by the clone:
$ cd VTK
Development
We provide here a brief introduction to development with Git. See the Resources below for further information.
First, use git config to introduce yourself to Git:
$ git config --global user.name "Your Name" $ git config --global user.email "you@yourdomain.com"
Optionally enable color output from Git commands:
$ git config --global color.ui auto
The --global option stores the configuration settings in ~/.gitconfig in your home directory so that they apply to all repositories.
Publishing
Authorized developers may publish work directly to public.kitware.com/vtk-tmp.git using Git's SSH protocol.
Authentication
All publishers share the git@public.kitware.com account but each uses a unique ssh key for authentication.
To request access, fill out the Kitware Password form.
Include your ssh public key and a reference to someone our administrators may contact to verify your privileges.
Note that we may not grant all contributors push access to the public.kitware.com repository.
The distributed nature of Git allows contributors to retain authorship credit even if they do not publish changes directly.
After the final conversion to Git is finished we will consider pull requests from online Git hosting sites.
Pushing
Git automatically configures a new clone to refer to its origin through a remote called origin.
Initially one may fetch or pull changes from origin,
but may not push changes to it.
In order to publish new commits in the public.kitware.com repository, developers must configure a push URL for the origin.
Use git config to specify an ssh-protocol URL:
$ git config remote.origin.pushurl git@public.kitware.com:vtk-tmp.git
(Note that 'pushurl' requires Git >= 1.6.4. Use just 'url' for Git < 1.6.4.)
Once your push URL is configured and your key is installed for git@public.kitware.com then you can try pushing changes.
Resources
Additional information about Git may be obtained at these sites:
