Lines Matching full:commit
30 Sometimes the patch you are backporting already exists as a git commit,
58 knows the precise history of an existing commit, so it will know when
80 commit <upstream commit> upstream
84 [ Upstream commit <upstream commit> ]
147 It's important to always identify the commit or commits that caused the
162 the patch you are picking (``<commit>``), i.e.::
164 git log HEAD..<commit>^ -- <path>
170 git log -L:'\<function\>':<path> HEAD..<commit>^
185 git log -G'regex' HEAD..<commit>^ -- <path>
199 need to run it against the parent commit of the patch you are
202 git blame <commit>^ -- <path>
208 git blame -L:'\<function\>' <commit>^ -- <path>
211 the blame output is the commit ID of the patch that added a given line
245 with the commit ID of the prerequisite patch instead.
262 >>>>>>> <commit>... title
274 ++>>>>>>>> <commit>... title
307 +>>>>>>>> <commit>... title
323 ||||||| parent of <commit> (title)
327 >>>>>>> <commit> (title)
333 of the file for the commit you are cherry-picking. This allows you to
408 (see the `rebase tutorial`_) so it appears as a single commit when you
484 colordiff -yw -W 200 <(git diff -W <upstream commit>^-) <(git diff -W HEAD^-) | less -SR
493 giving you just the diff for that single commit; also see
567 [ Upstream commit <mainline rev> ]
573 The "Upstream commit" line is sometimes slightly different depending on
576 commit <mainline rev> upstream.