ITK/Git/Download: Difference between revisions

From KitwarePublic
< ITK‎ | Git
Jump to navigationJump to search
No edit summary
No edit summary
Line 7: Line 7:


{| style="width: 100%"
{| style="width: 100%"
!width=60%|
!
|-
|-
|
|width=60%|
Clone ITK using the commands
Clone ITK using the commands
|-
|-
Line 42: Line 40:


{| style="width: 100%"
{| style="width: 100%"
!width=60%|
!
|-
|-
|
|width=60%|
Users that have made no local changes and simply want to update a
Users that have made no local changes and simply want to update a
clone with the latest changes may run
clone with the latest changes may run
Line 64: Line 60:


{| style="width: 100%"
{| style="width: 100%"
!width=60%|
!
|-
|-
|
|width=60%|
After cloning your local repository will be configured to follow the
After cloning your local repository will be configured to follow the
upstream '''master''' branch by default.
upstream '''master''' branch by default.

Revision as of 18:44, 17 November 2010

This page documents how to download ITK through Git. See our table of contents for more information.

Follow our Git download instructions to install Git.

Clone

Clone ITK using the commands

$ git clone git://itk.org/ITK.git
$ cd ITK

git help clone

Connection refused?

If you want to run tests, get the Testing/Data submodule:

$ git submodule update --init

git help submodule

Clone ITKApps using the commands

$ cd ..
$ git clone git://itk.org/ITKApps.git

git help clone

Update

Users that have made no local changes and simply want to update a clone with the latest changes may run

$ git pull
$ git submodule update

git help pull

git help submodule

Avoid making local changes unless you have read our developer instructions.

Release

After cloning your local repository will be configured to follow the upstream master branch by default. One may create a local branch to track the upstream release branch instead:

$ git checkout --track -b release origin/release
$ git submodule update

git help checkout

git help submodule

This local branch will always follow the latest release. Use the above instructions to update it. Alternatively one may checkout a specific release tag:

$ git checkout v3.20.0
$ git submodule update

git help checkout

git help submodule

Release tags never move. Repeat the command with a different tag to get a different release. One may list available tags:

$ git tag

git help tag