From: Eric Sunshine <sunshine@sunshineco.com>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 3/4] t5550-http-fetch-dumb.sh: use the GIT_TRACE_CURL environment var
Date: Mon, 5 Sep 2016 09:43:14 -0400 [thread overview]
Message-ID: <CAPig+cTsCDpCQ9j82OEa13YBYswDKfYd_dc1QbxRSRk3wiOhHw@mail.gmail.com> (raw)
In-Reply-To: <20160905102444.3586-4-gitter.spiros@gmail.com>
On Mon, Sep 5, 2016 at 6:24 AM, Elia Pinto <gitter.spiros@gmail.com> wrote:
> Use the new GIT_TRACE_CURL environment variable instead
> of the deprecated GIT_CURL_VERBOSE.
>
> Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
> ---
> diff --git a/t/t5550-http-fetch-dumb.sh b/t/t5550-http-fetch-dumb.sh
> @@ -263,15 +263,18 @@ check_language () {
> >expect
> ;;
> ?*)
> - echo "Accept-Language: $1" >expect
> + echo "=> Send header: Accept-Language: $1" >expect
> ;;
> esac &&
> - GIT_CURL_VERBOSE=1 \
> + GIT_TRACE_CURL=true \
> LANGUAGE=$2 \
> git ls-remote "$HTTPD_URL/dumb/repo.git" >output 2>&1 &&
> tr -d '\015' <output |
> sort -u |
> - sed -ne '/^Accept-Language:/ p' >actual &&
> + sed -ne '/^=> Send header: Accept-Language:/ p' >actual &&
> + cp expect expect.$$ &&
> + cp actual actual.$$ &&
> + cp output output.$$ &&
What are these three cp's about? They don't seem to be related to the
stated changes. Are they leftover debugging gunk?
> test_cmp expect actual
> }
>
> @@ -295,8 +298,8 @@ ja;q=0.95, zh;q=0.94, sv;q=0.93, pt;q=0.92, nb;q=0.91, *;q=0.90" \
> '
>
> test_expect_success 'git client does not send an empty Accept-Language' '
> - GIT_CURL_VERBOSE=1 LANGUAGE= git ls-remote "$HTTPD_URL/dumb/repo.git" 2>stderr &&
> - ! grep "^Accept-Language:" stderr
> + GIT_TRACE_CURL=true LANGUAGE= git ls-remote "$HTTPD_URL/dumb/repo.git" 2>stderr &&
> + ! grep "^=> Send header: Accept-Language:" stderr
> '
>
> stop_httpd
next prev parent reply other threads:[~2016-09-05 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 10:24 [PATCH 0/4] test suite: use the GIT_TRACE_CURL environment var Elia Pinto
2016-09-05 10:24 ` [PATCH 1/4] t5541-http-push-smart.sh: " Elia Pinto
2016-09-05 10:24 ` [PATCH 2/4] test-lib.sh: preserve GIT_TRACE_CURL from the environment Elia Pinto
2016-09-05 10:24 ` [PATCH 3/4] t5550-http-fetch-dumb.sh: use the GIT_TRACE_CURL environment var Elia Pinto
2016-09-05 13:43 ` Eric Sunshine [this message]
2016-09-05 19:09 ` Elia Pinto
2016-09-07 18:25 ` Junio C Hamano
2016-09-07 19:58 ` Junio C Hamano
2016-09-05 10:24 ` [PATCH 4/4] t5551-http-fetch-smart.sh: " Elia Pinto
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=CAPig+cTsCDpCQ9j82OEa13YBYswDKfYd_dc1QbxRSRk3wiOhHw@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@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).