From: Lars Schneider <larsxschneider@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jan 2017, #04; Mon, 23)
Date: Thu, 26 Jan 2017 10:14:01 +0100 [thread overview]
Message-ID: <D9F0976B-9F78-44BE-B9DD-CAB6506FA3A9@gmail.com> (raw)
In-Reply-To: <xmqq7f5i92jk.fsf@gitster.mtv.corp.google.com>
> 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
next prev parent reply other threads:[~2017-01-26 9:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 0:18 What's cooking in git.git (Jan 2017, #04; Mon, 23) Junio C Hamano
2017-01-24 10:04 ` Lars Schneider
2017-01-24 13:27 ` Jeff King
2017-01-24 14:43 ` Lars Schneider
2017-01-25 17:01 ` Johannes Schindelin
2017-01-25 17:39 ` Jeff King
2017-01-25 18:16 ` Junio C Hamano
2017-01-25 18:39 ` Jeff King
2017-01-25 22:51 ` Junio C Hamano
2017-01-26 9:14 ` Lars Schneider [this message]
2017-01-26 9:48 ` Lars Schneider
2017-01-26 14:26 ` Jeff King
2017-01-26 18:05 ` Junio C Hamano
2017-01-25 18:38 ` Stefan Beller
2017-01-25 20:35 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D9F0976B-9F78-44BE-B9DD-CAB6506FA3A9@gmail.com \
--to=larsxschneider@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).