public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Adam Blank <adam.blank.g@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Adam Blank <adam.blank.g@gmail.com>
Subject: [PATCH 0/4] Slight code cleanup - remove dead code, fix typos, unify patterns
Date: Thu, 02 Apr 2026 16:54:57 +0200	[thread overview]
Message-ID: <20260402-dead_code_and_unification-v1-0-5a3906b6340d@gmail.com> (raw)

Signed-off-by: Adam Blank <adam.blank.g@gmail.com>
---
Adam Blank (4):
      lib/packagedata.py: slight improvement to code readability
      package_pkgdata: fix typo to stop calling undefined function
      sstate: remove dead code and unify path operations
      package: update the comment block explaining 'emit_pkgdata'

 meta/classes-global/package.bbclass         | 3 +--
 meta/classes-global/package_pkgdata.bbclass | 4 +---
 meta/classes-global/sstate.bbclass          | 5 ++---
 meta/lib/oe/packagedata.py                  | 3 +--
 4 files changed, 5 insertions(+), 10 deletions(-)
---
base-commit: c56990178b31b893fbf695eaf6b67de501e9d2e9
change-id: 20260402-dead_code_and_unification-d2b31d998515

Best regards,
-- 
Adam Blank <adam.blank.g@gmail.com>



             reply	other threads:[~2026-04-02 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02 14:54 Adam Blank [this message]
2026-04-02 14:54 ` [PATCH 1/4] lib/packagedata.py: slight improvement to code readability Adam Blank
2026-04-02 14:54 ` [PATCH 2/4] package_pkgdata: fix typo to stop calling undefined function Adam Blank
2026-04-02 15:00   ` Patchtest results for " patchtest
2026-04-02 14:55 ` [PATCH 3/4] sstate: remove dead code and unify path operations Adam Blank
2026-04-02 14:55 ` [PATCH 4/4] package: update the comment block explaining 'emit_pkgdata' Adam Blank
2026-04-02 15:00   ` Patchtest results for " patchtest

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=20260402-dead_code_and_unification-v1-0-5a3906b6340d@gmail.com \
    --to=adam.blank.g@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