From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Pedro Ferreira <pedro.silva.ferreira@criticaltechworks.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH 4/4] sstate: Drop SSTATEPOSTINSTFUNC support
Date: Mon, 02 Sep 2024 13:01:59 +0100 [thread overview]
Message-ID: <999553313be2aa7be4e6e822f2e911aea9e2ede3.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240902103148.3762538-4-pedro.silva.ferreira@criticaltechworks.com>
On Mon, 2024-09-02 at 11:31 +0100, Pedro Ferreira wrote:
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> This was deprecated with the introduction of postfunc support for
> tasks
> in general and only used by buildhistory. Now that usage has been
> removed,
> drop the code from sstate.bbclass. Any other users should be able to
> use
> postfuncs too.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> meta/classes-global/sstate.bbclass | 6 ------
> 1 file changed, 6 deletions(-)
I suspect this patch can be dropped from the series as we wouldn't
remove this on a stable branch.
I'd also highlight that this has not merged to master yet.
Cheers,
Richard
next prev parent reply other threads:[~2024-09-02 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 10:31 [scarthgap][PATCH 1/4] buildhistory: Fix intermittent package file list creation Pedro Ferreira
2024-09-02 10:31 ` [scarthgap][PATCH 2/4] buildhistory: Restoring files from preserve list Pedro Ferreira
2024-09-02 10:31 ` [scarthgap][PATCH 3/4] buildhistory: Simplify intercept call sites and drop SSTATEPOSTINSTFUNC usage Pedro Ferreira
2024-09-02 10:31 ` [scarthgap][PATCH 4/4] sstate: Drop SSTATEPOSTINSTFUNC support Pedro Ferreira
2024-09-02 12:01 ` Richard Purdie [this message]
2024-09-03 13:19 ` [OE-core] [scarthgap][PATCH 1/4] buildhistory: Fix intermittent package file list creation Steve Sakoman
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=999553313be2aa7be4e6e822f2e911aea9e2ede3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pedro.silva.ferreira@criticaltechworks.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