Re: What's cooking in git.git (Jan 2017, #04; Mon, 23)

From: Lars Schneider <larsxschneider@gmail.com>
Date: Jan 26, 2017, 09:14 UTC
Message-ID: <D9F0976B-9F78-44BE-B9DD-CAB6506FA3A9@gmail.com>
In-Reply-To: <xmqq7f5i92jk.fsf@gitster.mtv.corp.google.com>

Show 9 quoted lines

> On 25 Jan 2017, at 23:51, Junio C Hamano <gitster@pobox.com> wrote:
> 
> Jeff King <peff@peff.net> writes:
> 
>> I guess the way to dig would be to add a test that looks at the output
>> of "type mv" or something, push it to a Travis-hooked branch, and then
>> wait for the output
> 
> Sounds tempting ;-)

Well, I tried that:

mv is /bin/mv

... and "/bin/mv" is exactly the version that I have on my machine.

The difference between Travis and my machine is that I changed the default shell to ZSH with a few plugins [1]. If I run the test with plain BASH on my Mac then I can reproduce the test failure. Therefore, we might want to adjust the commit message if anyone else can reproduce the problem on a Mac.

I can even reproduce the failure if I run the test with plain ZSH. However, I can't find a plugin that defines an alias for "mv". Puzzled...

- Lars

[1] https://github.com/robbyrussell/oh-my-zsh