From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: David Aguilar <davvid@gmail.com>, Git ML <git@vger.kernel.org>,
Denton Liu <liu.denton@gmail.com>
Subject: Re: [PATCH] difftool: fix bug when printing usage
Date: Tue, 07 Feb 2017 12:06:48 -0800 [thread overview]
Message-ID: <xmqqd1etzrxj.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqh945zs3c.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Tue, 07 Feb 2017 12:03:19 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>>> > Likewise, this would become
>>> >
>>> > GIT_CEILING_DIRECTORIES="$PWD/not" \
>>> > test_expect_code 129 git -C not/repo difftool -h >output &&
>>> > grep ^usage: output
>>>
>>> I agree with the intent, but the execution here is "Not quite".
>>> test_expect_code being a shell function, it does not take the
>>> "one-shot environment assignment for this single invocation," like
>>> external commands do.
>>
>> So now that we know what is wrong, can you please enlighten me about what
>> is right?
>
> David's original is just fine, isn't it?
I've also seen people use "env VAR=VAL git command" as the command
to be tested in t/ scripts. You can run that under test_expect_code,
methinks.
next prev parent reply other threads:[~2017-02-07 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 2:56 [PATCH] Remove --no-gui option from difftool usage string Denton Liu
2017-02-04 5:58 ` Jacob Keller
2017-02-04 6:23 ` Denton Liu
2017-02-05 10:22 ` David Aguilar
2017-02-05 20:17 ` [BUG] was: " David Aguilar
2017-02-05 21:23 ` [PATCH] difftool: fix bug when printing usage David Aguilar
2017-02-06 16:58 ` Johannes Schindelin
2017-02-06 18:13 ` Junio C Hamano
2017-02-07 11:21 ` Johannes Schindelin
2017-02-07 20:03 ` Junio C Hamano
2017-02-07 20:06 ` Junio C Hamano [this message]
2017-02-08 15:06 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqd1etzrxj.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).