From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: Anders Roxell <anders.roxell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Beraldo Leal <bleal@redhat.com>
Subject: Re: [RFC PATCH] tests/docker: merge debian-native with debian-amd64
Date: Wed, 8 Nov 2023 18:35:07 +0100 [thread overview]
Message-ID: <039a6e2d-8daf-46a4-a175-8df1ceaef0c3@linaro.org> (raw)
In-Reply-To: <20231108165602.3865524-1-alex.bennee@linaro.org>
On 8/11/23 17:56, Alex Bennée wrote:
> debian-native isn't really needed and suffers from the problem of
> tracking a distros dependencies rather than the projects. With a
> little surgery we can make the debian-amd64 container architecture
> neutral and allow people to use it to build a native QEMU.
>
> Rename it so it follows the same non-arch pattern of the other distro
> containers.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Anders Roxell <anders.roxell@linaro.org>
> ---
> .gitlab-ci.d/buildtest.yml | 12 ++---
> .gitlab-ci.d/containers.yml | 2 +-
> tests/docker/Makefile.include | 3 --
> tests/docker/dockerfiles/debian-native.docker | 54 -------------------
> .../{debian-amd64.docker => debian.docker} | 7 ++-
> tests/lcitool/refresh | 9 ++--
> 6 files changed, 18 insertions(+), 69 deletions(-)
> delete mode 100644 tests/docker/dockerfiles/debian-native.docker
> rename tests/docker/dockerfiles/{debian-amd64.docker => debian.docker} (96%)
Good idea. Why RFC?
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-11-08 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 16:56 [RFC PATCH] tests/docker: merge debian-native with debian-amd64 Alex Bennée
2023-11-08 17:35 ` Philippe Mathieu-Daudé [this message]
2023-11-08 18:37 ` Alex Bennée
2023-11-08 20:56 ` Anders Roxell
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=039a6e2d-8daf-46a4-a175-8df1ceaef0c3@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=bleal@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).