Added 3 extra tests for the bash.showDirtyState config option, tests
should now cover all combinations of the shell var being set/unset and
the config option being enabled/disabled, given a dirty file.
* Renamed test 'disabled by config' to 'shell variable set with config
disabled' for
Martin Erik Werner martinerikwer...@gmail.com writes:
Added 3 extra tests for the bash.showDirtyState config option, tests
should now cover all combinations of the shell var being set/unset and
the config option being enabled/disabled, given a dirty file.
Strictly speaking, you have 6 not 4
On Wed, 2013-02-13 at 08:28 -0800, Junio C Hamano wrote:
Martin Erik Werner martinerikwer...@gmail.com writes:
Added 3 extra tests for the bash.showDirtyState config option, tests
should now cover all combinations of the shell var being set/unset and
the config option being
Martin Erik Werner martinerikwer...@gmail.com writes:
Strictly speaking, you have 6 not 4 combinations (shell variable
set/unset * config missing/set to false/set to true). I think these
additional tests cover should all 6 because config missing case
should already have had tests before
On Wed, 2013-02-13 at 11:53 -0800, Junio C Hamano wrote:
Martin Erik Werner martinerikwer...@gmail.com writes:
Strictly speaking, you have 6 not 4 combinations (shell variable
set/unset * config missing/set to false/set to true). I think these
additional tests cover should all 6 because
Martin Erik Werner martinerikwer...@gmail.com writes:
OK, I'll locally amend the patch. Thanks.
Ok, so I shouldn't reroll them with s/unset -v/sane_unset/ and reworded
commits + sign-off then, I can if you prefer that?
You can if you wanted to. That would be less work for me ;-).
--
To
6 matches
Mail list logo
