Lines Matching full:git

4 patches with Gerrit, using Gerrit dependency chains, and managing local git
9 The instructions in [README.md](README.md) using `git cl upload` are preferred
11 review system via `git` if you prefer as follows.
18 to track changes.  Once installed, this can be toggled with `git config
25   curl -Lo .git/hooks/commit-msg https://chromium-review.googlesource.com/tools/hooks/commit-msg
26   chmod a+x .git/hooks/commit-msg
31 You should run `git cl presubmit --upload` in the root of the repository before pushing for
35 `git cl upload`, which will prompt you to verify the commit message and check
40 …nch, not the commit). See the [git-cl](https://chromium.googlesource.com/chromium/tools/depot_tool…
56   git checkout featureA
57   git checkout -b featureB
58   git branch --set-upstream-to featureA
60   # ... git add ...
61   git commit
64 The git history then looks something like this:
74 and `git log` might show:
95 git push origin HEAD:refs/for/master
102 ## Examples for maintaining local git history
129 git checkout C
130 git checkout -b M
131 git rebase -i origin/master # squash commits
133 # it.  You can git commit --amend with the commit-msg hook active or add it via
134 # git commit --amend after pushing.  Don't git commit --amend after creating N
136 git push origin HEAD:refs/for/master
137 git checkout E
138 git checkout -b N
139 git rebase -i C --onto M # squash commits
140 git push origin HEAD:refs/for/master
141 git checkout G
142 git checkout -b O
143 git rebase -i origin/master # squash commits and copy the Change-Id line from M
144 git push origin HEAD:refs/for/master
168 git checkout H
169 git checkout -b P
170 git rebase -i origin/master # squash commits, same note as M about Change-Id
171 git push origin HEAD:refs/for/master
172 git checkout featureB # E
173 git rebase # assume featureA is set as featureB's upstream branch
174 git checkout -b Q
175 git rebase -i H --onto P
176 git push origin HEAD:refs/for/master