summaryrefslogtreecommitdiff
path: root/t/t5321-pack-large-objects.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2019-07-31 08:18:45 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-07-31 12:24:07 -0700
commita9c71073dace0d1ddbd12291604d191064b1ae94 (patch)
treeb6336b2967847c34d97e3be55b79361823616dda /t/t5321-pack-large-objects.sh
parentt3427: condense the unnecessarily repetitive test cases into three (diff)
downloadtgif-a9c71073dace0d1ddbd12291604d191064b1ae94.tar.xz
t3427: fix erroneous assumption
Apart from the `setup` test case, `t3427-rebase-subtree.sh` is made up exclusively of demonstrations of breakages. The tricky thing about such demonstrations is that they are often buggy themselves. In this instance, somewhere over the course of the six iterations of the patch that eventually made it into Git's `master` as 5f35900849e (contrib/subtree: Add a test for subtree rebase that loses commits, 2016-06-28), the commit message "files_subtree/master4" was changed to just "master4", but the test cases still expected the old commit message. Let's fix this, at long last. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5321-pack-large-objects.sh')
0 files changed, 0 insertions, 0 deletions