From: Junio C Hamano Date: Wed, 9 Mar 2011 23:56:17 +0000 (-0800) Subject: Merge branch 'js/cherry-pick-usability' X-Git-Tag: v1.7.5-rc0~88 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/66ecd2d05306fccc65e8d6a5f49100840ea7d3b6?ds=inline;hp=-c Merge branch 'js/cherry-pick-usability' * js/cherry-pick-usability: Teach commit about CHERRY_PICK_HEAD bash: teach __git_ps1 about CHERRY_PICK_HEAD Introduce CHERRY_PICK_HEAD t3507: introduce pristine-detach helper --- 66ecd2d05306fccc65e8d6a5f49100840ea7d3b6 diff --combined Documentation/git-cherry-pick.txt index 749d68a72b,cd848664ce..5d85daa5fe --- a/Documentation/git-cherry-pick.txt +++ b/Documentation/git-cherry-pick.txt @@@ -16,6 -16,25 +16,25 @@@ Given one or more existing commits, app introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit). + When it is not obvious how to apply a change, the following + happens: + + 1. The current branch and `HEAD` pointer stay at the last commit + successfully made. + 2. The `CHERRY_PICK_HEAD` ref is set to point at the commit that + introduced the change that is difficult to apply. + 3. Paths in which the change applied cleanly are updated both + in the index file and in your working tree. + 4. For conflicting paths, the index file records up to three + versions, as described in the "TRUE MERGE" section of + linkgit:git-merge[1]. The working tree files will include + a description of the conflict bracketed by the usual + conflict markers `<<<<<<<` and `>>>>>>>`. + 5. No other modifications are made. + + See linkgit:git-merge[1] for some hints on resolving such + conflicts. + OPTIONS ------- ...:: @@@ -79,16 -98,6 +98,16 @@@ effect to your index in a row cherry-pick'ed commit, then a fast forward to this commit will be performed. +--strategy=:: + Use the given merge strategy. Should only be used once. + See the MERGE STRATEGIES section in linkgit:git-merge[1] + for details. + +-X