From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] ci: clear and mark MAKEFLAGS exported just once
Date: Fri, 8 Feb 2019 01:17:10 +0100 [thread overview]
Message-ID: <20190208001710.GS10587@szeder.dev> (raw)
In-Reply-To: <xmqqd0o3mac5.fsf_-_@gitster-ct.c.googlers.com>
On Thu, Feb 07, 2019 at 03:45:46PM -0800, Junio C Hamano wrote:
> Clearing it once upfront, and turning all the assignment into
> appending, would future-proof the code even more, to prevent
> mistakes the previous one fixed from happening again.
>
> Also, mark the variable exported just once at the beginning. There
> is no point in marking it exported repeatedly.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> >> So I'd rather clear `MAKEFLAGS` at the beginning (i.e. where you `export
> >> MAKEFLAGS`, I'd simply append a `=`).
>
> This time in proper patch form.
Makes sense, and the patch looks good to me.
> ci/lib.sh | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/ci/lib.sh b/ci/lib.sh
> index cee51a4cc4..288a5b3884 100755
> --- a/ci/lib.sh
> +++ b/ci/lib.sh
> @@ -74,6 +74,9 @@ check_unignored_build_artifacts ()
> }
> }
>
> +# Clear MAKEFLAGS that may come from the outside world.
> +export MAKEFLAGS=
> +
> # Set 'exit on error' for all CI scripts to let the caller know that
> # something went wrong.
> # Set tracing executed commands, primarily setting environment variables
> @@ -101,7 +104,7 @@ then
> BREW_INSTALL_PACKAGES="git-lfs gettext"
> export GIT_PROVE_OPTS="--timer --jobs 3 --state=failed,slow,save"
> export GIT_TEST_OPTS="--verbose-log -x --immediate"
> - export MAKEFLAGS="--jobs=2"
> + MAKEFLAGS="$MAKEFLAGS --jobs=2"
> elif test -n "$SYSTEM_COLLECTIONURI" || test -n "$SYSTEM_TASKDEFINITIONSURI"
> then
> CI_TYPE=azure-pipelines
> @@ -126,7 +129,7 @@ then
> BREW_INSTALL_PACKAGES=gcc@8
> export GIT_PROVE_OPTS="--timer --jobs 10 --state=failed,slow,save"
> export GIT_TEST_OPTS="--verbose-log -x --write-junit-xml"
> - export MAKEFLAGS="--jobs=10"
> + MAKEFLAGS="$MAKEFLAGS --jobs=10"
> test windows_nt != "$CI_OS_NAME" ||
> GIT_TEST_OPTS="--no-chain-lint --no-bin-wrappers $GIT_TEST_OPTS"
> else
> @@ -185,4 +188,4 @@ GIT_TEST_GETTEXT_POISON)
> ;;
> esac
>
> -export MAKEFLAGS="$MAKEFLAGS CC=${CC:-cc}"
> +MAKEFLAGS="$MAKEFLAGS CC=${CC:-cc}"
> --
> 2.21.0-rc0
>
next prev parent reply other threads:[~2019-02-08 0:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 18:37 [PATCH] ci: make sure we build Git parallel SZEDER Gábor
2019-02-07 19:00 ` Junio C Hamano
2019-02-07 19:04 ` Junio C Hamano
2019-02-07 19:35 ` Junio C Hamano
2019-02-07 22:32 ` Johannes Schindelin
2019-02-07 23:33 ` Junio C Hamano
2019-02-07 23:45 ` [PATCH] ci: clear and mark MAKEFLAGS exported just once Junio C Hamano
2019-02-08 0:17 ` SZEDER Gábor [this message]
2019-02-08 10:11 ` Johannes Schindelin
2019-02-08 10:10 ` [PATCH] ci: make sure we build Git parallel Johannes Schindelin
2019-02-08 17:25 ` 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=20190208001710.GS10587@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).