summaryrefslogtreecommitdiff
path: root/t/t0062-revision-walking.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2021-01-28 16:16:42 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-01-28 12:12:37 -0800
commitf7d42ceec5265f6dbcaeb527657521b7ec8ddc94 (patch)
treed12d9ae0d8ae3189fa378a6c08125da20d705f57 /t/t0062-revision-walking.sh
parentGit 2.30 (diff)
downloadtgif-f7d42ceec5265f6dbcaeb527657521b7ec8ddc94.tar.xz
rebase -i: do leave commit message intact in fixup! chains
In 6e98de72c03 (sequencer (rebase -i): add support for the 'fixup' and 'squash' commands, 2017-01-02), this developer introduced a change of behavior by mistake: when encountering a `fixup!` commit (or multiple `fixup!` commits) without any `squash!` commit thrown in, the final `git commit` was invoked with `--cleanup=strip`. Prior to that commit, the commit command had been called without that `--cleanup` option. Since we explicitly read the original commit message from a file in that case, there is really no sense in forcing that clean-up. We actually need to actively suppress that clean-up lest a configured `commit.cleanup` may interfere with what we want to do: leave the commit message unchanged. Reported-by: Vojtěch Knyttl <vojtech@knyt.tl> Helped-by: Martin Ågren <martin.agren@gmail.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t0062-revision-walking.sh')
0 files changed, 0 insertions, 0 deletions