summaryrefslogtreecommitdiff
path: root/Documentation/SubmittingPatches
diff options
context:
space:
mode:
authorLibravatar Phil Hord <hordp@cisco.com>2012-02-21 19:44:17 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-02-22 11:13:43 -0800
commited727b192bb3506ee7904c1c9e8370d6b4ecaf5d (patch)
treede21fef09f9d9bcbc64f28b194d0b23c3f9b46e4 /Documentation/SubmittingPatches
parentMerge branch 'rr/sequencer' (diff)
downloadtgif-ed727b192bb3506ee7904c1c9e8370d6b4ecaf5d.tar.xz
cherry-pick: No advice to commit if --no-commit
When cherry-pick fails it offers a helpful hint about how to proceed. The hint tells the user how to do the cleanup needed by the conflicted cherry-pick and finish the job after conflict resolution. In case of cherry-pick --no-commit, the hint goes too far. It tells the user to finish up with 'git commit'. That is not what this git-cherry-pick was trying to do in the first place. Restrict the hint in case of --no-commit to avoid giving this extra advice. Also, add a test verifying the reduced hint for the --no-commit version of cherry-pick. Signed-off-by: Phil Hord <hordp@cisco.com> Acked-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/SubmittingPatches')
0 files changed, 0 insertions, 0 deletions