ITK/Git/Download: Difference between revisions

From KitwarePublic
< ITK‎ | Git
Jump to navigationJump to search
No edit summary
(Add the historical label after Change-Id I5b79451da962c95614c65e09679bc8b5c12b6dea was merged)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{ Historical }}
This page documents how to download ITK through [http://git-scm.com Git].
This page documents how to download ITK through [http://git-scm.com Git].
See our [[ITK/Git|table of contents]] for more information.
See our [[ITK/Git|table of contents]] for more information.
Line 7: Line 9:


{| style="width: 100%"
{| style="width: 100%"
!width=60%|
!
|-
|-
|
|width=60%|
Clone ITK using the commands
Clone ITK using the commands
|-
|-
Line 17: Line 17:
:<code>$ cd ITK</code>
:<code>$ cd ITK</code>
|align="center"|
|align="center"|
[http://www.kernel.org/pub/software/scm/git/docs/git-clone.html <code>git help clone</code>]
[http://schacon.github.com/git/git-clone.html <code>git help clone</code>]


[[Git/Trouble#Firewall_Blocks_Port_9418|Connection refused]]?
[[Git/Trouble#Firewall_Blocks_Port_9418|Connection refused]]?
|-
|
If you want to run tests, get the <code>Testing/Data</code> submodule:
|-
|
:<code>$ git submodule update --init</code>
|align="center"|
[http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html <code>git help submodule</code>]
|-
|-
|
|
Line 36: Line 28:
:<code>$ git clone git://itk.org/ITKApps.git</code>
:<code>$ git clone git://itk.org/ITKApps.git</code>
|align="center"|
|align="center"|
[http://www.kernel.org/pub/software/scm/git/docs/git-clone.html <code>git help clone</code>]
[http://schacon.github.com/git/git-clone.html <code>git help clone</code>]
|}
|}


Line 42: Line 34:


{| 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 51: Line 41:
|
|
:<code>$ git pull</code>
:<code>$ git pull</code>
:<code>$ git submodule update</code>
|align="center"|
|align="center"|
[http://www.kernel.org/pub/software/scm/git/docs/git-pull.html <code>git help pull</code>]
[http://schacon.github.com/git/git-pull.html <code>git help pull</code>]


[http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html <code>git help submodule</code>]
|-
|-
|
|
Line 64: Line 52:


{| 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. This means you will have access to cutting edge features, but along with these may come cutting edge bugs :). One may create a local branch to track the upstream '''release''' branch instead, which should guarantee only bug fixes to the functionality available in the latest release:
One may create a local branch to track the upstream '''release'''
branch instead:
|-
|-
|
|
:<code>$ git checkout --track -b release origin/release</code>
:<code>$ git checkout --track -b release origin/release</code>
:<code>$ git submodule update</code>
|align="center"|
|align="center"|
[http://www.kernel.org/pub/software/scm/git/docs/git-checkout.html <code>git help checkout</code>]
[http://schacon.github.com/git/git-checkout.html <code>git help checkout</code>]


[http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html <code>git help submodule</code>]
|-
|-
|
|
Line 90: Line 72:
:<code>$ git submodule update</code>
:<code>$ git submodule update</code>
|align="center"|
|align="center"|
[http://www.kernel.org/pub/software/scm/git/docs/git-checkout.html <code>git help checkout</code>]
[http://schacon.github.com/git/git-checkout.html <code>git help checkout</code>]


[http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html <code>git help submodule</code>]
[http://schacon.github.com/git/git-submodule.html <code>git help submodule</code>]
|-
|-
|
|
Line 102: Line 84:
:<code>$ git tag</code>
:<code>$ git tag</code>
|align="center"|
|align="center"|
[http://www.kernel.org/pub/software/scm/git/docs/git-tag.html <code>git help tag</code>]
[http://schacon.github.com/git/git-tag.html <code>git help tag</code>]
|}
|}

Latest revision as of 14:54, 6 October 2017

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?

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 help pull

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. This means you will have access to cutting edge features, but along with these may come cutting edge bugs :). One may create a local branch to track the upstream release branch instead, which should guarantee only bug fixes to the functionality available in the latest release:

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

git help checkout

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

Retrieved from "https://public.kitware.com/Wiki/index.php?title=ITK/Git/Download&oldid=62059"