From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <bcasey@nvidia.com>
Cc: <git@vger.kernel.org>, <ralf.thielow@gmail.com>,
Brandon Casey <drafnel@gmail.com>
Subject: Re: [PATCH] t7502: perform commits using alternate editor in a subshell
Date: Fri, 22 Feb 2013 15:24:28 -0800 [thread overview]
Message-ID: <7vliagaq4z.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1361574780-30067-1-git-send-email-bcasey@nvidia.com> (Brandon Casey's message of "Fri, 22 Feb 2013 15:13:00 -0800")
Brandon Casey <bcasey@nvidia.com> writes:
> From: Brandon Casey <drafnel@gmail.com>
>
> These tests call test_set_editor to set an alternate editor script, but
> they appear to presume that the assignment is of a temporary nature and
> will not have any effect outside of each individual test. That is not
> the case. All of the test functions within a test script share a single
> environment, so any variables modified in one, are visible in the ones
> that follow.
>
> So, let's protect the test functions that follow these, which set an
> alternate editor, by performing the test_set_editor and 'git commit'
> in a subshell.
>
> Signed-off-by: Brandon Casey <drafnel@gmail.com>
> ---
>
>
> Before "git-commit: populate the edit buffer with 2 blank lines before s-o-b"
> is merged, this is needed on top of rt/commit-cleanup-config 51fb3a3d so that
> the default EDITOR remains in effect for the new test.
Yeah, what I already pushed out forces EDITOR=: for your test for
the same effect, but this patch clearly takes us in the right (and
better) direction.
>
> -Brandon
>
>
> t/t7502-commit.sh | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/t/t7502-commit.sh b/t/t7502-commit.sh
> index b1c7648..520a5cd 100755
> --- a/t/t7502-commit.sh
> +++ b/t/t7502-commit.sh
> @@ -255,32 +255,40 @@ test_expect_success 'cleanup commit message (fail on invalid cleanup mode config
> test_expect_success 'cleanup commit message (no config and no option uses default)' '
> echo content >>file &&
> git add file &&
> - test_set_editor "$TEST_DIRECTORY"/t7500/add-content-and-comment &&
> - git commit --no-status &&
> + (
> + test_set_editor "$TEST_DIRECTORY"/t7500/add-content-and-comment &&
> + git commit --no-status
> + ) &&
> commit_msg_is "commit message"
> '
>
> test_expect_success 'cleanup commit message (option overrides default)' '
> echo content >>file &&
> git add file &&
> - test_set_editor "$TEST_DIRECTORY"/t7500/add-content-and-comment &&
> - git commit --cleanup=whitespace --no-status &&
> + (
> + test_set_editor "$TEST_DIRECTORY"/t7500/add-content-and-comment &&
> + git commit --cleanup=whitespace --no-status
> + ) &&
> commit_msg_is "commit message # comment"
> '
>
> test_expect_success 'cleanup commit message (config overrides default)' '
> echo content >>file &&
> git add file &&
> - test_set_editor "$TEST_DIRECTORY"/t7500/add-content-and-comment &&
> - git -c commit.cleanup=whitespace commit --no-status &&
> + (
> + test_set_editor "$TEST_DIRECTORY"/t7500/add-content-and-comment &&
> + git -c commit.cleanup=whitespace commit --no-status
> + ) &&
> commit_msg_is "commit message # comment"
> '
>
> test_expect_success 'cleanup commit message (option overrides config)' '
> echo content >>file &&
> git add file &&
> - test_set_editor "$TEST_DIRECTORY"/t7500/add-content-and-comment &&
> - git -c commit.cleanup=whitespace commit --cleanup=default &&
> + (
> + test_set_editor "$TEST_DIRECTORY"/t7500/add-content-and-comment &&
> + git -c commit.cleanup=whitespace commit --cleanup=default
> + ) &&
> commit_msg_is "commit message"
> '
prev parent reply other threads:[~2013-02-22 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 23:13 [PATCH] t7502: perform commits using alternate editor in a subshell Brandon Casey
2013-02-22 23:24 ` Junio C Hamano [this message]
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=7vliagaq4z.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bcasey@nvidia.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=ralf.thielow@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.
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).