summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2016-08-04 16:54:35 +0200
committerJunio C Hamano <gitster@pobox.com>2016-08-04 10:18:36 -0700
commit9eed4f3711a605ab2d9b986357879a09a6d54f36 (patch)
tree76eed05dd1bce6f73895b238904762656047b504
parent64ac39af7020f3a8bc52d51137804ce9f46baf66 (diff)
downloadgit-jk/push-force-with-lease-creation.tar.gz
t5533: make it pass on case-sensitive filesystemsjk/push-force-with-lease-creation
The newly-added test case wants to commit a file "c.t" (note the lower case) when a previous test case already committed a file "C.t". This confuses Git to the point that it thinks "c.t" was not staged when "git add c.t" was called. Simply make the naming of the test commits consistent with the previous test cases: use upper-case, and advance in the alphabet. This came up in local work to rebase the Windows-specific patches to the current `next` branch. An identical fix was suggested by John Keeping. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rwxr-xr-xt/t5533-push-cas.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/t/t5533-push-cas.sh b/t/t5533-push-cas.sh
index 09899af3b0..a2c9e7439f 100755
--- a/t/t5533-push-cas.sh
+++ b/t/t5533-push-cas.sh
@@ -220,7 +220,7 @@ test_expect_success 'new branch already exists' '
(
cd src &&
git checkout -b branch master &&
- test_commit c
+ test_commit F
) &&
(
cd dst &&