From: Tim Orling <ticotimo@gmail.com>
To: yocto@lists.yoctoproject.org
Cc: bluelightning@bluelightning.org
Subject: [layerindex-web][PATCH 0/3] Fixes for updates
Date: Sun, 24 Apr 2022 14:10:06 -0700 [thread overview]
Message-ID: <cover.1650833930.git.tim.orling@konsulko.com> (raw)
This series includes fixes to allow update.py to run on 'master', by
providing a check for the BB_ENV_PASSTHROUGHS_ADDITIONS variable
renaming in bitbake 2.0+.
To do so, an 'is_commit_ancestor' check is added to allow for checking
if a particular commit hash is present in a checked out repo (e.g.
bitbake).
Also included is an improvement on the prior patch to ignore 'core' in
BBFILES_COLLECTIONS (logging a debug message rather than a warning for
the case where 'core' is ignored).
The following changes since commit 4dd7f0ee8f31df927c3862677dc59636988d8dfd:
layerindex/models.py: add Inactive-Upstream (2022-04-18 12:56:51 -0700)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web timo/fixes2
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=timo/fixes2
Tim Orling (3):
layerindex/utils.py: add is_commit_ancestor check
recipe{desc,parse}.py: BB_ENV_PASSTHROUGH_ADDITIONS
layerindex/utils.py: ignore 'core' in BBFILES_COLLECTIONS
layerindex/recipedesc.py | 8 +++++++-
layerindex/recipeparse.py | 7 ++++++-
layerindex/utils.py | 29 ++++++++++++++++++++++++++++-
3 files changed, 41 insertions(+), 3 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-25 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 21:10 Tim Orling [this message]
2022-04-24 21:10 ` [layerindex-web][PATCH 1/3] layerindex/utils.py: add is_commit_ancestor check Tim Orling
2022-04-28 14:58 ` [layerindex-web][PATCH v2 " Tim Orling
2022-04-24 21:10 ` [layerindex-web][PATCH v2 2/3] recipe{desc,parse}.py: BB_ENV_PASSTHROUGH_ADDITIONS Tim Orling
2022-04-24 21:10 ` [layerindex-web][PATCH v2 3/3] layerindex/utils.py: ignore 'core' in BBFILES_COLLECTIONS Tim Orling
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.1650833930.git.tim.orling@konsulko.com \
--to=ticotimo@gmail.com \
--cc=bluelightning@bluelightning.org \
--cc=yocto@lists.yoctoproject.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.