From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] t9301-fast-export.sh: don't unset config variable while we're skipping test 4
Date: Mon, 18 Aug 2008 17:32:45 -0700 [thread overview]
Message-ID: <7vtzdhkfo2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <kbCw6MBjduXNz0eWrsdfGIVr60qjr7cf1eJqhd4l-UzDfHEk1LrlkA@cipher.nrlssc.navy.mil> (Brandon Casey's message of "Mon, 18 Aug 2008 18:20:12 -0500")
Brandon Casey <casey@nrlssc.navy.mil> writes:
> ---
>
>
> This is necessary if t9301.4 is included in the GIT_SKIP_TESTS
> environment variable.
If it is not skipped what happens? Does your change break this test?
How about attempting to unset always (because the test does not want to
have the configuration) but ignore the result from the command (because
the config may not have had anything to unset to begin with depending on
what happened in the previous tests)?
> t/t9301-fast-export.sh | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/t/t9301-fast-export.sh b/t/t9301-fast-export.sh
> index c19b4a2..475aadd 100755
> --- a/t/t9301-fast-export.sh
> +++ b/t/t9301-fast-export.sh
> @@ -190,7 +190,6 @@ export GIT_COMMITTER_NAME='C O Mitter'
>
> test_expect_success 'setup copies' '
>
> - git config --unset i18n.commitencoding &&
> git checkout -b copy rein &&
> git mv file file3 &&
> git commit -m move1 &&
> --
> 1.6.0.13.ge1c8
next prev parent reply other threads:[~2008-08-19 0:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 22:55 [FYI] How I compile on IRIX 6.5 with the MIPSpro compiler and ksh Brandon Casey
2008-08-18 23:02 ` [PATCH] Makefile: add section for SGI IRIX Brandon Casey
2008-08-18 23:05 ` [PATCH] git-compat-util.h: adjust for SGI IRIX 6.5 Brandon Casey
2008-08-18 23:09 ` [PATCH] unpack-trees.c: work around run-time array initialization flaw on " Brandon Casey
2008-08-18 23:14 ` [PATCH] templates/Makefile: work around SGI install which assumes / if ROOT not defined Brandon Casey
2008-08-18 23:37 ` Junio C Hamano
2008-08-19 0:52 ` Brandon Casey
2008-08-22 0:31 ` [PATCH] templates/Makefile: install is unnecessary, just use mkdir -p Brandon Casey
2008-08-18 23:16 ` [PATCH] test-lib.sh: work around ksh's trap shortcomings Brandon Casey
2008-08-18 23:48 ` Junio C Hamano
2008-08-19 0:06 ` Brandon Casey
2008-08-19 7:39 ` Junio C Hamano
2008-08-19 14:59 ` Brandon Casey
2008-08-19 1:27 ` Brandon Casey
2008-08-20 0:19 ` Brandon Casey
2008-08-20 11:36 ` Mike Ralphson
2008-08-18 23:17 ` [PATCH] t1002-read-tree-m-u-2way.sh: use 'git diff -U0' rather than 'diff -U0' Brandon Casey
2008-08-18 23:20 ` [PATCH] t9301-fast-export.sh: don't unset config variable while we're skipping test 4 Brandon Casey
2008-08-19 0:32 ` Junio C Hamano [this message]
2008-08-19 0:39 ` Brandon Casey
2008-08-22 0:48 ` [PATCH] t9301-fast-export: move unset of config variable into its own test function Brandon Casey
2008-08-22 8:18 ` Junio C Hamano
2008-08-22 8:23 ` Junio C Hamano
2008-08-22 9:02 ` Johannes Sixt
2008-08-22 21:11 ` Junio C Hamano
2008-08-18 23:51 ` [FYI] How I compile on IRIX 6.5 with the MIPSpro compiler and ksh Brandon Casey
2008-08-19 1:18 ` Boyd Lynn Gerber
2008-08-19 1:25 ` Brandon Casey
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=7vtzdhkfo2.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
/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).