[Insight-developers] Gerrit / git primer

[Matthew McCormick (thewtex)]

Dan,

>
> http://www.itk.org/Wiki/ITK/Gerrit/Primer
>
> Very nice.

It seems that it is not necessary to squash a branch into a single commit,
though, because of changes that were made to Gerrit?  When a topic branch is
pushed, all commits in a branch are identified with a branch name in the
commits overview.  This can be clicked to show all commits belonging to a
branch.

I have been learning Gerrit for the past couple of days while working with
Brad King, aka Eagle Eye ;-).   After figuring it out, it is quite fun,
primarily because it is such an efficient way to work and interact.

Some things I stumbled over:

- Keeping clear the difference between a git commit hash, a gerrit Change
Id, and a gerrit change number.  The git commit hash is the sha hash that
identifies the commit in git.  The gerrit Change Id looks similar, but it
starts with an I.  It is used to identify the commit in gerrit.  There
should be one, and only one, Change Id that lives at the end of a commit
message.  The gerrit change number is a small number used to identify the
commit when pushing to gerrit.

- When replying to inline comments, they are only visible to the world after
going to the commit's review page, hitting the 'Review' button, then hitting
'Publish Comments'.

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20100916/9d8f3541/attachment-0001.htm>