From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Fabio Berton <fbberton@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] buildhistory.bbclass: restore BUILDHISTORY_PRESERVE files
Date: Wed, 25 Jun 2025 11:46:20 +0100 [thread overview]
Message-ID: <64bb84dc0d44185080fbd0f8a2c8bd4e6cff4987.camel@linuxfoundation.org> (raw)
In-Reply-To: <12213779-fcd9-4091-b340-44eb200bc97f@gmail.com>
On Wed, 2025-06-25 at 11:26 +0100, Fabio Berton wrote:
> Thanks for looking into this. I was wondering if there is a way to
> know whether BUILDHISTORY_PRESERVE, or another variable, is not
> intended to be part of the end user API?
This is something we struggle with and don't have well defined. A sign
in this case is that it isn't in the manual though...
Cheers,
Richard
prev parent reply other threads:[~2025-06-25 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 15:31 [PATCH] buildhistory.bbclass: restore BUILDHISTORY_PRESERVE files Pedro Ferreira
2025-01-22 13:42 ` [OE-core] " Ross Burton
2025-01-23 14:37 ` Pedro Ferreira
2025-03-06 14:26 ` Pedro Ferreira
2025-03-12 13:40 ` [OE-core] " Ross Burton
2025-06-23 20:48 ` Richard Purdie
2025-06-25 10:26 ` Fabio Berton
2025-06-25 10:46 ` Richard Purdie [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=64bb84dc0d44185080fbd0f8a2c8bd4e6cff4987.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=fbberton@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox