summaryrefslogtreecommitdiff
path: root/blob.c
diff options
context:
space:
mode:
authorLibravatar Samuel Čavoj <samuel@cavoj.net>2020-10-18 01:15:55 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-10-18 13:08:31 -0700
commitae03c97ac0e36a33183562464f9506c8b3a73060 (patch)
treebb3dd39cac6bf83feedbe2f29a13e06de8409229 /blob.c
parentGit 2.29-rc1 (diff)
downloadtgif-ae03c97ac0e36a33183562464f9506c8b3a73060.tar.xz
sequencer: fix gpg option passed to merge subcommand
When performing a rebase with --rebase-merges using either a custom strategy specified with -s or an octopus merge, and at the same time having gpgsign enabled (either rebase -S or config commit.gpgsign), the operation would fail on making the merge commit. Instead of "-S%s" with the key id substituted, only the bare key id would get passed to the underlying merge command, which tried to interpret it as a ref. Fix the issue and add test cases as suggested by Johannes Schindelin and Junio C Hamano. Signed-off-by: Samuel Čavoj <samuel@cavoj.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'blob.c')
0 files changed, 0 insertions, 0 deletions