ITK/Git/Download: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(Created page with "This page documents how to download ITK through [http://git-scm.com Git]. See our table of contents for more information. =Clone= {| style="width: 100%" !width=60%|...") |
Jhlegarreta (talk | contribs) (Add the historical label after Change-Id I5b79451da962c95614c65e09679bc8b5c12b6dea was merged) |
||
| (9 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. | ||
Follow our [[Git/Download|Git download instructions]] to install Git. | |||
=Clone= | =Clone= | ||
{| style="width: 100%" | {| style="width: 100%" | ||
|- | |- | ||
| | |width=60%| | ||
Clone ITK using the commands | Clone ITK using the commands | ||
|- | |- | ||
| Line 15: | Line 17: | ||
:<code>$ cd ITK</code> | :<code>$ cd ITK</code> | ||
|align="center"| | |align="center"| | ||
[http:// | [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]]? | ||
|- | |- | ||
| | | | ||
| Line 34: | 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:// | [http://schacon.github.com/git/git-clone.html <code>git help clone</code>] | ||
|} | |} | ||
| Line 40: | Line 34: | ||
{| style="width: 100%" | {| style="width: 100%" | ||
|- | |- | ||
| | |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 49: | Line 41: | ||
| | | | ||
:<code>$ git pull</code> | :<code>$ git pull</code> | ||
|align="center"| | |align="center"| | ||
[http:// | [http://schacon.github.com/git/git-pull.html <code>git help pull</code>] | ||
|- | |- | ||
| | | | ||
Avoid making local changes unless you have read our [[ITK/Git/Develop|developer instructions]]. | |||
|} | |} | ||
| Line 62: | Line 52: | ||
{| style="width: 100%" | {| style="width: 100%" | ||
|- | |- | ||
| | |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> | ||
|align="center"| | |align="center"| | ||
[http:// | [http://schacon.github.com/git/git-checkout.html <code>git help checkout</code>] | ||
|- | |- | ||
| | | | ||
| Line 88: | Line 72: | ||
:<code>$ git submodule update</code> | :<code>$ git submodule update</code> | ||
|align="center"| | |align="center"| | ||
[http:// | [http://schacon.github.com/git/git-checkout.html <code>git help checkout</code>] | ||
[http:// | [http://schacon.github.com/git/git-submodule.html <code>git help submodule</code>] | ||
|- | |- | ||
| | | | ||
| Line 100: | Line 84: | ||
:<code>$ git tag</code> | :<code>$ git tag</code> | ||
|align="center"| | |align="center"| | ||
[http:// | [http://schacon.github.com/git/git-tag.html <code>git help tag</code>] | ||
|} | |} | ||
Latest revision as of 14:54, 6 October 2017
 | This page is currently inactive and is retained for historical reference. Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the village pump. |
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 | |
|
|
|
Clone ITKApps using the commands | |
|
Update
|
Users that have made no local changes and simply want to update a clone with the latest changes may run | |
|
|
|
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: | |
|
|
|
This local branch will always follow the latest release. Use the above instructions to update it. Alternatively one may checkout a specific release tag: | |
|
|
|
Release tags never move. Repeat the command with a different tag to get a different release. One may list available tags: | |
|
