summaryrefslogtreecommitdiff
path: root/t/perf/bisect_run_script
diff options
context:
space:
mode:
authorLibravatar Paolo Bonzini <pbonzini@redhat.com>2020-02-20 15:15:19 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-02-20 13:20:41 -0800
commitaa416b22ea73321aba94c3c96db0491fb25ea7ea (patch)
treea0e3e1c9f67208bfbdf6666da0221a1574c9d52a /t/perf/bisect_run_script
parentam: support --show-current-patch=raw as a synonym for--show-current-patch (diff)
downloadtgif-aa416b22ea73321aba94c3c96db0491fb25ea7ea.tar.xz
am: support --show-current-patch=diff to retrieve .git/rebase-apply/patch
When "git am --show-current-patch" was added in commit 984913a210 ("am: add --show-current-patch", 2018-02-12), "git am" started recommending it as a replacement for .git/rebase-merge/patch. Unfortunately the suggestion is somewhat misguided; for example, the output of "git am --show-current-patch" cannot be passed to "git apply" if it is encoded as quoted-printable or base64. Add a new mode to "git am --show-current-patch" in order to straighten the suggestion. Reported-by: J. Bruce Fields <bfields@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/perf/bisect_run_script')
0 files changed, 0 insertions, 0 deletions