Add a test that feeds "diff-tree --stdin <pathspec>" with list of revisions, in a way very similar to how "gitk" drives it. If we had such a test, we would have caught the recent regression. Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> --- * On top of that "revert" change. t/t4013-diff-various.sh | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/t/t4013-diff-various.sh b/t/t4013-diff-various.sh index 750aee17ea..628b01f355 100755 --- a/t/t4013-diff-various.sh +++ b/t/t4013-diff-various.sh @@ -542,6 +542,20 @@ test_expect_success 'diff-tree --stdin with log formatting' ' test_cmp expect actual ' +test_expect_success 'diff-tree --stdin with pathspec' ' + cat >expect <<-EOF && + Third + + dir/sub + Second + + dir/sub + EOF + git rev-list master^ | + git diff-tree -r --stdin --name-only --format=%s dir >actual && + test_cmp expect actual +' + test_expect_success 'diff -I<regex>: setup' ' git checkout master && test_seq 50 >file0 && -- 2.36.0-200-g3c19986797
