From: <liezhi.yang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [PATCH v2 0/1] classes: Print bitbake branch and revision
Date: Wed, 11 Sep 2024 06:10:22 -0700 [thread overview]
Message-ID: <cover.1726059965.git.liezhi.yang@windriver.com> (raw)
From: Robert Yang <liezhi.yang@windriver.com>
* 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 (1):
classes: Print bitbake branch and revision
meta/classes-global/base.bbclass | 10 +++++++---
meta/classes/buildhistory.bbclass | 5 +++--
meta/classes/image-buildinfo.bbclass | 13 +++++++++++--
meta/lib/oe/buildcfg.py | 13 +++++++++++++
4 files changed, 34 insertions(+), 7 deletions(-)
--
2.44.1
WARNING: multiple messages have this Message-ID (diff)
From: <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH v2 0/1] classes: Print bitbake branch and revision
Date: Wed, 11 Sep 2024 06:13:26 -0700 [thread overview]
Message-ID: <cover.1726059965.git.liezhi.yang@windriver.com> (raw)
From: Robert Yang <liezhi.yang@windriver.com>
* 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 (1):
classes: Print bitbake branch and revision
meta/classes-global/base.bbclass | 10 +++++++---
meta/classes/buildhistory.bbclass | 5 +++--
meta/classes/image-buildinfo.bbclass | 13 +++++++++++--
meta/lib/oe/buildcfg.py | 13 +++++++++++++
4 files changed, 34 insertions(+), 7 deletions(-)
--
2.44.1
next reply other threads:[~2024-09-11 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 13:10 liezhi.yang [this message]
2024-09-11 13:13 ` [PATCH v2 0/1] classes: Print bitbake branch and revision liezhi.yang
2024-09-11 13:10 ` [PATCH v2 1/1] " liezhi.yang
2024-09-11 13:13 ` liezhi.yang
2024-09-11 14:14 ` [OE-core] " Alexander Kanavin
2024-09-11 14:30 ` Robert Yang
2024-09-11 14:37 ` Alexander Kanavin
2024-09-11 13:14 ` [oe] [PATCH v2 0/1] " 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.1726059965.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-devel@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.