All of lore.kernel.org
 help / color / mirror / Atom feed
From: <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: <alex.kanavin@gmail.com>
Subject: [PATCH v3 0/2] classes: Print bitbake branch and revision
Date: Wed, 11 Sep 2024 07:35:58 -0700	[thread overview]
Message-ID: <cover.1726065189.git.liezhi.yang@windriver.com> (raw)

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

* V3:
  - Add is_bitbake_in_separate_repo() as Alexander suggested

* V2:
  - Move the code out of get_layer_revisions() as Alexander suggested 
  - Always print bitbake branch and revision to make the output consistent
    whenever bitbake is in a separate repo or not.

* V1:
  - Initial version

// Robert

The following changes since commit 918e2b266eba6779f19f65349f85caa880ba45e7:

  libedit: Make docs generation deterministic (2024-09-11 11:56:34 +0100)

are available in the Git repository at:

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

Robert Yang (2):
  classes: Print bitbake branch and revision
  lib/buildcfg: Add is_bitbake_in_separate_repo()

 meta/classes-global/base.bbclass     | 10 +++++++---
 meta/classes/buildhistory.bbclass    |  5 +++--
 meta/classes/image-buildinfo.bbclass | 13 +++++++++++--
 meta/lib/oe/buildcfg.py              | 23 +++++++++++++++++++++++
 4 files changed, 44 insertions(+), 7 deletions(-)

-- 
2.44.1



             reply	other threads:[~2024-09-11 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 14:35 liezhi.yang [this message]
2024-09-11 14:35 ` [PATCH v3 1/2] classes: Print bitbake branch and revision liezhi.yang
2024-09-17 11:12   ` [OE-core] " Richard Purdie
2024-09-18  7:56     ` Robert Yang
2024-09-11 14:36 ` [PATCH v3 2/2] lib/buildcfg: Add is_bitbake_in_separate_repo() liezhi.yang
2024-09-12  5:13   ` [OE-core] " Peter Kjellerstedt
2024-09-12  9:10     ` Robert 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.1726065189.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=alex.kanavin@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 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.