All of lore.kernel.org
 help / color / mirror / Atom feed
From: <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH v2 0/1] buildhistory.bbclass: Warn when PRSERV_HOST is not enabled
Date: Sun, 16 Nov 2025 17:23:01 -0800	[thread overview]
Message-ID: <cover.1763342137.git.liezhi.yang@windriver.com> (raw)

From: Robert Yang <liezhi.yang@windriver.com>

* V2:
  - Only warn when version-going-backwards is enabled as RP suggested.

* V1:
  - Initial version

// Robert

The following changes since commit e7dc42e30c76bf0fbb4d3cc019bbec675bac55fa:

  oe-build-perf-report: relax metadata matching rules (2025-11-16 23:44:30 +0000)

are available in the Git repository at:

  https://github.com/robertlinux/yocto rbt/warn
  https://github.com/robertlinux/yocto/tree/rbt/warn

Robert Yang (1):
  buildhistory.bbclass: Warn when PRSERV_HOST is not enabled

 meta/classes/buildhistory.bbclass | 7 +++++++
 1 file changed, 7 insertions(+)

-- 
2.49.0



             reply	other threads:[~2025-11-17  1:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17  1:23 liezhi.yang [this message]
2025-11-17  1:23 ` [PATCH v2 1/1] buildhistory.bbclass: Warn when PRSERV_HOST is not enabled liezhi.yang

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=cover.1763342137.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.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 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.