Code

tests: do not rely on external "patch"
authorJunio C Hamano <gitster@pobox.com>
Sun, 20 Jul 2008 08:33:46 +0000 (01:33 -0700)
committerJunio C Hamano <gitster@pobox.com>
Tue, 22 Jul 2008 04:33:16 +0000 (21:33 -0700)
commitac2e28c0a43ced3837fbbcf66fd693244b6c6693
tree7b620d45d6768297ad4188be755704aae83da1b5
parentc79cc2e59672fa03985f27ecdbea84e06ea5358f
tests: do not rely on external "patch"

Some of our tests assumed a working "patch" command to produce expected
results when checking "git-apply", but some systems have broken "patch".

We can compare our output with expected output that is precomputed
instead to sidestep this issue.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t4109-apply-multifrag.sh
t/t4109/expect-1 [new file with mode: 0644]
t/t4109/expect-2 [new file with mode: 0644]
t/t4109/expect-3 [new file with mode: 0644]
t/t4110-apply-scan.sh
t/t4110/expect [new file with mode: 0644]
t/t4110/patch1.patch [new file with mode: 0644]
t/t4110/patch2.patch [new file with mode: 0644]
t/t4110/patch3.patch [new file with mode: 0644]
t/t4110/patch4.patch [new file with mode: 0644]
t/t4110/patch5.patch [new file with mode: 0644]