From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v2 1/4] support/testing/tests/package/test_docker-compose: fix docker compose binary name
Date: Tue, 1 Nov 2022 21:17:21 +0100 [thread overview]
Message-ID: <20221101211721.7ee3298a@windsurf> (raw)
In-Reply-To: <20221031232752.626154-1-christian@paral.in>
On Mon, 31 Oct 2022 16:27:49 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
> Docker compose is now invoked as "docker compose" not "docker-compose."
>
> Signed-off-by: Christian Stewart <christian@paral.in>
> ---
> support/testing/tests/package/test_docker_compose.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, series applied, after adding a reference to the Gitlab CI job
being fixed by the first patch into its commit log. Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-01 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 23:27 [Buildroot] [PATCH v2 1/4] support/testing/tests/package/test_docker-compose: fix docker compose binary name Christian Stewart via buildroot
2022-10-31 23:27 ` [Buildroot] [PATCH v2 2/4] support/testing/tests/package/test_docker-compose: fix docker compose container name Christian Stewart via buildroot
2022-10-31 23:27 ` [Buildroot] [PATCH v2 3/4] support/testing/tests/package/test_docker-compose: quiet overly verbose output Christian Stewart via buildroot
2022-10-31 23:27 ` [Buildroot] [PATCH v2 4/4] support/testing/tests/package/test_docker-compose: update kernel to 4.19.262 Christian Stewart via buildroot
2022-11-01 20:17 ` Thomas Petazzoni via buildroot [this message]
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=20221101211721.7ee3298a@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.