60.
rebase ( commit )‧git rebase -i e37c7578pick 048b59e first commitpick 995dbb3 change somethingpick aa3e16e changed# Rebase 0072886..1b6475f onto 0072886## Commands:# p, pick = use commit# r, reword = use commit, but edit the commit message# e, edit = use commit, but stop for amending# s, squash = use commit, but meld into previous commit# f, fixup = like "squash", but discard this commits log message# x, exec = run command (the rest of the line) using shell## If you remove a line here THAT COMMIT WILL BE LOST.# However, if you remove everything, the rebase will be aborted. 52

111.
the maintainer workﬂow for git itself http://www.kernel.org/pub/software/scm/git/docs/gitworkﬂows.html‧master tracks the commits that should go into the next release‧maint tracks the commits that should go into the next "maintenance release"‧next is intended as a testing branch for topics being tested for stability for master.‧pu (proposed updates branches) is an integration branch for things that are not quite ready for inclusion yet‧topic branches for any nontrivial feature99

115.
‧http://progit.org/book/‧http://git-scm.com‧http://help.github.com/‧http://gitimmersion.com‧http://www.gitready.com/‧http://gitref.org‧http://ihower.tw/blog/category/git‧Pragmatic Version Control Using Git, Pragmatic 103