From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCH v3 4/4] classes: fix comment in container-img class
Date: Mon, 2 Aug 2021 13:54:04 +0200 [thread overview]
Message-ID: <20210802115404.22707-5-henning.schild@siemens.com> (raw)
In-Reply-To: <20210802115404.22707-1-henning.schild@siemens.com>
The task name is in fact a different one, the function sits in another
class.
Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
meta/classes/container-img.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/container-img.bbclass b/meta/classes/container-img.bbclass
index 9928a58ef53d..edd0e7f8f932 100644
--- a/meta/classes/container-img.bbclass
+++ b/meta/classes/container-img.bbclass
@@ -3,7 +3,7 @@
#
# SPDX-License-Identifier: MIT
#
-# This class provides the task 'containerize_rootfs'
+# This class provides the task 'container_image'
# to create container images containing the target rootfs.
do_container_image[stamp-extra-info] = "${DISTRO}-${MACHINE}"
--
2.31.1
prev parent reply other threads:[~2021-08-02 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 11:54 [PATCH v3 0/4] Allow better control over container tags Henning Schild
2021-08-02 11:54 ` [PATCH v3 1/4] classes: make sure container extension can run multiple times Henning Schild
2021-08-02 11:54 ` [PATCH v3 2/4] classes: simplify tag handling in container class Henning Schild
2021-08-02 11:54 ` [PATCH v3 3/4] classes: allow more control over container image name and tag Henning Schild
2021-08-02 12:26 ` Silvano Cirujano Cuesta
2021-08-02 13:14 ` Henning Schild
2021-08-02 13:27 ` Silvano Cirujano Cuesta
2021-08-05 16:01 ` Henning Schild
2021-08-02 11:54 ` Henning Schild [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=20210802115404.22707-5-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=silvano.cirujano-cuesta@siemens.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