All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/5] buildhistory: Only use image-artifact-names as an image class
Date: Wed, 10 Aug 2022 20:45:06 +0100	[thread overview]
Message-ID: <20220810194510.484900-1-richard.purdie@linuxfoundation.org> (raw)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 meta/classes/buildhistory.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/buildhistory.bbclass b/meta/classes/buildhistory.bbclass
index 4ba9ec8f25d..35db2b11927 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -7,7 +7,7 @@
 # Copyright (C) 2007-2011 Koen Kooi <koen@openembedded.org>
 #
 
-inherit image-artifact-names
+IMAGE_CLASSES += "image-artifact-names"
 
 BUILDHISTORY_FEATURES ?= "image package sdk"
 BUILDHISTORY_DIR ?= "${TOPDIR}/buildhistory"
-- 
2.34.1



             reply	other threads:[~2022-08-10 19:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 19:45 Richard Purdie [this message]
2022-08-10 19:45 ` [PATCH 2/5] classes: Add copyright statements to files without one Richard Purdie
2022-08-10 19:45 ` [PATCH 3/5] scripts: " Richard Purdie
2022-08-10 19:45 ` [PATCH 4/5] classes: Add SPDX license identifiers Richard Purdie
2022-08-10 19:45 ` [PATCH 5/5] lib: Add copyright statements to files without one Richard Purdie
2022-08-11  7:57   ` Paul Barker
2022-08-11  7:59     ` Richard Purdie
2022-08-11  8:19       ` Paul Barker
2022-08-11 14:14         ` Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2022-08-10 19:59 [PATCH 1/5] buildhistory: Only use image-artifact-names as an image class Richard Purdie

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=20220810194510.484900-1-richard.purdie@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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.