On 12/04/2019 13:13, Mark Thomas wrote:
> On 12/04/2019 09:56, Mark Thomas wrote:
>> On 12/04/2019 01:32, Igal Sapir wrote:
>>> Mark,
>>>
>>> I just realized that you refactored my fix for the false positive unit test
>>> [1] a while ago. Unfortunately your refactoring still shows false
>>> positi
On 12/04/2019 09:56, Mark Thomas wrote:
> On 12/04/2019 01:32, Igal Sapir wrote:
>> Mark,
>>
>> I just realized that you refactored my fix for the false positive unit test
>> [1] a while ago. Unfortunately your refactoring still shows false
>> positives if the path of the command prompt has a lowe
On 12/04/2019 01:32, Igal Sapir wrote:
> Mark,
>
> I just realized that you refactored my fix for the false positive unit test
> [1] a while ago. Unfortunately your refactoring still shows false
> positives if the path of the command prompt has a lower-cased driver
> letter, e.g.
>
> expected: b
Mark,
I just realized that you refactored my fix for the false positive unit test
[1] a while ago. Unfortunately your refactoring still shows false
positives if the path of the command prompt has a lower-cased driver
letter, e.g.
expected: but
was:
I pushed a different fix earlier, prior to no
