| commit | a700395eaf7aaa833c0643f7f741603c56893edd | |
| author | Martin Ågren <martin.agren@gmail.com> | |
| Mon, 18 Jul 2022 15:43:22 +0000 (18 17:43 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 18 Jul 2022 18:01:54 +0000 (18 11:01 -0700) | ||
| tree | 55ad04443a08ceb59e3497b441e63d4ce1be2c43 | treesnapshot (tar.gz zip) |
| parent | bbea4dcf42b28eb7ce64a6306cdde875ae5d09ca | commitdiff |
t4200: drop irrelevant code
While setting up an unresolved merge for `git rerere`, we run `git
rev-parse` and `git fmt-merge-msg` to create a variable `$fifth` and a
commit-message file `msg`, which we then never actually use. This has
been like that since these tests were added in 672d1b789b ("rerere:
migrate to parse-options API", 2010-08-05). This does exercise `git
rev-parse` and `git fmt-merge-msg`, but doesn't contribute to testing
`git rerere`. Drop these lines.
Reported-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Martin Ågren <martin.agren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
While setting up an unresolved merge for `git rerere`, we run `git
rev-parse` and `git fmt-merge-msg` to create a variable `$fifth` and a
commit-message file `msg`, which we then never actually use. This has
been like that since these tests were added in 672d1b789b ("rerere:
migrate to parse-options API", 2010-08-05). This does exercise `git
rev-parse` and `git fmt-merge-msg`, but doesn't contribute to testing
`git rerere`. Drop these lines.
Reported-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Martin Ågren <martin.agren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t4200-rerere.sh | diffblobblamehistory |