git.99rst.org / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 356ee46)
t3512/t3513: remove KNOWN_FAILURE_CHERRY_PICK_SEES_EMPTY_COMMIT=1
authorPhillip Wood <redacted>
Fri, 24 Nov 2017 11:07:58 +0000 (11:07 +0000)
committerJunio C Hamano <redacted>
Fri, 24 Nov 2017 13:44:18 +0000 (22:44 +0900)
commitdb9476b50348c9d7e6a076cf4bd9ce0e70995439
treef3cf67328e5cc8523ae083141426a3415016154atree | snapshot
parent356ee4659bb551cd9464b317d691827276752c2dcommit | diff
t3512/t3513: remove KNOWN_FAILURE_CHERRY_PICK_SEES_EMPTY_COMMIT=1

Now that the sequencer creates commits without forking 'git commit' it
does not see an empty commit in these tests which fixes the known
breakage. Note that logic for handling
KNOWN_FAILURE_CHERRY_PICK_SEES_EMPTY_COMMIT=1 is not removed from
lib-submodule-update.sh as it is still used by other tests.

Signed-off-by: Phillip Wood <redacted>
Signed-off-by: Junio C Hamano <redacted>
t/t3512-cherry-pick-submodule.sh diff | blob | history
t/t3513-revert-submodule.sh diff | blob | history
git clone https://git.99rst.org/PROJECT