From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Willian Rampazzo <willianr@redhat.com>,
Thomas Huth <thuth@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
qemu-devel@nongnu.org,
Wainer dos Santos Moschetta <wainersm@redhat.com>
Subject: Re: [PATCH 5/9] gitlab-ci: explicitly reference the upstream registry
Date: Tue, 25 May 2021 12:10:55 +0100 [thread overview]
Message-ID: <87v9772hm6.fsf@linaro.org> (raw)
In-Reply-To: <20210525082556.4011380-6-f4bug@amsat.org>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> From: Alex Bennée <alex.bennee@linaro.org>
>
> Since c8e6793903 ("containers.yml: build with docker.py tooling") we
> don't need to manually pull stuff from the upstream repository. Just
> set the -r field to explicitly use that rather than the current
> registry.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Message-Id: <20210520174303.12310-3-alex.bennee@linaro.org>
> Reviewed-by: Willian Rampazzo <willianr@redhat.com>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> [PMD: Rebased]
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
FWIW this should get merged with today's PR.
--
Alex Bennée
next prev parent reply other threads:[~2021-05-25 11:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 8:25 [PATCH 0/9] gitlab-ci: Make mainstream CI green again Philippe Mathieu-Daudé
2021-05-25 8:25 ` [PATCH 1/9] gitlab-ci: Extract all default build/test jobs to buildtest.yml Philippe Mathieu-Daudé
2021-05-25 11:05 ` Alex Bennée
2021-05-25 8:25 ` [PATCH 2/9] gitlab-ci: Move current job set to qemu-project.yml Philippe Mathieu-Daudé
2021-05-25 11:05 ` Alex Bennée
2021-05-25 8:25 ` [PATCH 3/9] gitlab-ci: Document how forks can use different set of jobs Philippe Mathieu-Daudé
2021-05-25 11:06 ` Alex Bennée
2021-05-25 14:30 ` Willian Rampazzo
2021-05-25 8:25 ` [PATCH 4/9] gitlab-ci: Extract cross-container jobs to container-cross.yml Philippe Mathieu-Daudé
2021-05-25 11:06 ` Alex Bennée
2021-05-25 14:32 ` Willian Rampazzo
2021-05-25 8:25 ` [PATCH 5/9] gitlab-ci: explicitly reference the upstream registry Philippe Mathieu-Daudé
2021-05-25 11:10 ` Alex Bennée [this message]
2021-05-25 11:39 ` Philippe Mathieu-Daudé
2021-05-25 8:25 ` [PATCH 6/9] gitlab-ci: Split gprof-gcov job Philippe Mathieu-Daudé
2021-05-25 10:21 ` Philippe Mathieu-Daudé
2021-05-27 6:03 ` Thomas Huth
2021-05-27 13:04 ` Alex Bennée
2021-05-25 14:34 ` Willian Rampazzo
2021-06-07 11:36 ` Alex Bennée
2021-05-25 8:25 ` [PATCH 7/9] gitlab-ci: Keep Avocado reports during 1 week Philippe Mathieu-Daudé
2021-05-25 11:11 ` Alex Bennée
2021-05-25 14:35 ` Willian Rampazzo
2021-05-25 8:25 ` [PATCH 8/9] gitlab-ci: Run Avocado tests manually (except mainstream CI) Philippe Mathieu-Daudé
2021-05-25 11:25 ` Alex Bennée
2021-05-27 6:08 ` Thomas Huth
2021-05-25 8:25 ` [PATCH 9/9] gitlab-ci: Use absolute path and simplify firmware jobs Philippe Mathieu-Daudé
2021-05-25 8:56 ` Daniel P. Berrangé
2021-05-25 9:02 ` Philippe Mathieu-Daudé
2021-05-27 16:04 ` [PATCH 0/9] gitlab-ci: Make mainstream CI green again Philippe Mathieu-Daudé
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=87v9772hm6.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@redhat.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).