|(41 intermediate revisions by 9 users not shown)|
ITK version tracking and development is hosted by [http://git-scm.com Git].
One may browse the repository online using the [http://git.wiki.kernel.org/index.php/Gitweb Gitweb] interface at http://itk.org/gitweb.
Clone ITK using the command
$ git clone git://itk.org/ITK.git
If your institution's firewall blocks the Git port for outgoing connections you may see an error similar to:
Initialized empty Git repository in C:/abc/ITK/.git/itk.org[0: 184.108.40.206]:
errno=No such file or directory
fatal: unable to connect a socket (No such file or directory)
In that case, see [[#Firewall_Blocks_Port_9418|below]].
If you want to run tests, add the <code>--recursive</code> option to download the <code>Testing/Data</code> submodule.
$ git clone --recursive git://itk.org/ITK.git
This requires Git 1.6.5 or higher. If you do not have it, see [[#Git Below 1.6.5|below]].
All further commands work inside the local copy of the repository created by the clone:
$ cd ITK
If you already cloned and want to add the <code>Testing/Data</code> submodule then run
$ git submodule update --init
For ITKApps, use the url
If you have made no local commits and simply want to update your clone with the latest changes, run
$ git pull
$ git submodule update
If you know you do not have the <code>Testing/Data</code> submodule checked out then you can skip the submodule update command.
At the time of this writing the repository has the following branches:
* '''master''': Development (default)
* '''release''': Release maintenance
* '''nightly-master''': Follows '''master''', updated at 01:00 UTC
* '''hooks''': Local commit hooks ([[Git/Hooks#Local|place]] in .git/hooks)
* '''dashboard''': Dashboard script (see [[#Dashboard|below]])
Release branches converted from CVS have been artificially merged into master.
Actual releases have tags named by the release version number.
After cloning your local repository will be configured to follow the upstream '''master''' branch by default.
One may create a local branch to track another upstream branch using [http://www.kernel.org/pub/software/scm/git/docs/git-checkout.html git checkout]:
$ git checkout -b release origin/release
As a shortcut with Git >= 1.6.5 one may choose a branch during the initial clone:
$ git clone -b release git://itk.org/ITK.git ITKRel
We provide here a brief introduction to '''ITK''' development with Git.
See the [[Git/Resources|Resources]] page for further information such as Git tutorials.
We require all commits in ITK to record valid author/committer name and email information.
ITK and [http://git-.]
Use [http:/ /www.kernel.org/pub/software/scm/git/docs/git- config. html git config] to introduce yourself to Git:
$ git config --global user.name " Your Name"
$ git config --global user.email "firstname.lastname@example.org"
Note that "Your Name" is your ''real name'' (e.g. "John Doe", not "jdoe").
While you're at it, optionally enable color output from Git commands:
$ git config --global color.ui auto
If less displays strange characters and no color, your LESS environment variable may already be set. You can override the less options with:
$ git config --global core.pager "less - FXRS"
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 '''hooks''' branch provides local commit hooks to be placed in <code>.git/hooks</code>.
It is shared by many <code>public.kitware.com</code> repositories.
See the general [[Git/Hooks| hooks]] information page to set up your local hooks.
We've chosen to approximate our previous CVS-based development workflow after the initial move to Git, at least while things get settled.
The basic rule is to rebase your work on origin/master before pushing:
git fetch origin
git rebase origin/master
git pull --rebase
The server will refuse your push if it contains any merges.
Later we will move to a full [[Git/Workflow/Topic| branchy workflow]] based on topic branches.
We provide a "[http://itk.org/stage/ITK.git ITK Topic Stage]" repository to which developers may publish arbitrary topic branches and request automatic merges.
The topic stage URLs are
* <code>git: //itk.org/stage/ITK.git</code> (clone, fetch)
* <code>http://itk.org/stage/ITK.git</code> (clone, fetch, gitweb)
* <code>email@example.com:stage/ITK.git</code> (push)
See our [http://public.kitware.com/Wiki/Git/Workflow/Stage Topic Stage Workflow] documentation for general instructions.
''(Currently ITK does not have a '''next''' branch. Just skip that part of the instructions and merge directly to master.)''
When accessing the ITK stage, one may optionally substitute
"<code>ssh firstname.lastname@example.org stage ITK ...</code>"
"<code>ssh email@example.com stage <repo> ...</code>"
in the ssh command-line interface.
!colspan=2|Stage Usage Summary
$ git remote add stage git: //itk. org/ stage/ ITK.git
$ git config remote.stage.pushurl git@itk. org:stage/ITK. git
'''Fetch Staged Topics:'''
$ git fetch stage -- prune
'''Create Local Topic:'''
$ git checkout - b ''topic- name'' origin/ master
$ edit files
$ git commit
'''Stage Current Topic:'''
$ git push stage HEAD
'''Print Staged Topics:'''
$ ssh git@itk. org stage ITK print
'''Merge Staged Topic:'''
$ ssh git@itk. org stage ITK merge ''topic- name''
Note that the stage implementation is not ITK-specific and is used for other projects too.
is not instructions.''
If the merge attempt conflicts it may print instructions for performing the merge manually.
'Ignore''' these instructions; you will not be able to push the merge commit directly.
Instead, identify the commit that conflicts with yours, merge it into your topic locally, push the topic to the stage again, and then repeat the merge request.
Authorized developers may publish work directly to <code>itk.org/ITK.git</code> using Git's SSH protocol.
To request access, fill out the [https:// www. kitware. com/ Admin/ SendPassword. cgi Kitware Password] form.
See the [[Git/Publish#Push_Access|push instructions]] for details.
For ITK , configure the push URL:
git config remote. origin. pushurl git @itk.org:ITK .git
For ITKApps, configure the push URL:
have by the .
git config remote.origin.pushurl firstname.lastname@example.org:ITKApps.git
The itk.org repository has an <code>update</code> hook.
When someone tries to push changes to the repository it checks the commits as documented [[Git/Hooks#update|here]].
The [[#Branches| dashboard]] branch contains a dashboard client helper script.
Use these commands to track it:
$ mkdir -p ~/Dashboards/ITKScripts
$ cd ~/Dashboards/ITKScripts
$ git init
$ git remote add -t dashboard origin git://itk.org/ITK.git
$ git pull origin
The <code>itk_common.cmake</code> script contains setup instructions in its top comments.
Update the '''dashboard''' branch to get the latest version of this script by simply running
$ git pull origin
= Contributing Patches =
== Generating a Patch ==
== Applying a Patch ==
==Firewall Blocks Port 9418==
Some institutions have firewalls that block Git's native protocol port 9418.
Use the "<code>url.<base>.insteadOf</code>" configuration option to map git URLs to http:
$ git config --global url.http://itk.org/.insteadOf git://itk.org/
This tells Git to translate URLs under the hood by replacing prefixes.
After running these commands ''once'' in your home directory then you can just use the "<code>git://</code>" mentioned elsewhere on this page and git will use the http protocol automagically.
==Git Below 1.6.5==
To clone ITK using Git 1.6.4 or lower, use the commands
$ git clone git://itk.org/ITK.git
$ cd ITK
$ git submodule init
$ git submodule update
== The remote end hung up unexpectedly ==
If <code>git push</code> fails with
fatal: The remote end hung up unexpectedly
check that you set the pushurl with "<code>git config</code>".
See the [[#Pushing|push instructions]].
If you suspect your ssh key may not be configured correctly, see the [[Git/Publish#Authentication_Test|authentication test]] instructions.
Git does not explicitly track renames. The command
$ git mv old new
is equivalent to
$ mv old new
$ git add new
$ git rm old
Neither approach records the rename outright.
However, Git's philosophy is "''dumb add, smart view''".
It uses heuristics to ''detect'' renames when viewing history after-the-fact.
It even works when the content of a renamed file changes slightly.
In order to help Git efficiently detect the rename, it is important to remove the old file and add the new one in ''one commit'', perhaps by using <code>git mv</code> or the above 3-step procedure.
If the new file were added in one commit and the old file removed in the next, Git would report this as a copy followed by a removal.
It's copy-detection heuristics are more computationally intensive and must be explicitly enabled with the <code>-C</code> option to relevant operations (such as <code>git blame</code>).
Additional information about Git may be obtained at sites listed [[Git/Resources|here]].