bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 0/8] Patch review
Date: Tue, 19 Oct 2021 10:06:08 -1000	[thread overview]
Message-ID: <cover.1634673786.git.steve@sakoman.com> (raw)

Please review this next set of patches for dunfell/1.46 and have comments
back by end of day Thursday.

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2772

The following changes since commit b4117231bf070703b9375af4411bcd160e07fdae:

  build/msg: Cleanup verbose option handling (2021-09-30 04:12:50 -1000)

are available in the Git repository at:

  git://git.openembedded.org/bitbake-contrib stable/1.46-nut
  http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/1.46-nut

Alexander Kanavin (5):
  bitbake: correct the collections vs collections.abc deprecation
  bitbake: fix regexp deprecation warnings
  bitbake: do not import imp in layerindexlib
  bitbake: adjust parser error check for python 3.10 compatibility
  bitbake: correct deprecation warning in process.py

Chris Laplante (1):
  compat.py: remove file since it no longer actually implements anything

Justin Bronder (1):
  hashserv: let asyncio discover the running loop

Richard Purdie (1):
  test/fetch: Update urls to match upstream branch name changes

 lib/bb/compat.py              | 10 ----------
 lib/bb/data_smart.py          |  4 ++--
 lib/bb/event.py               | 16 ++++++++--------
 lib/bb/persist_data.py        | 13 +++++++------
 lib/bb/server/process.py      |  2 +-
 lib/bb/tests/event.py         | 17 +++++++++--------
 lib/bb/tests/fetch.py         |  6 +++---
 lib/bblayers/query.py         |  6 +++---
 lib/hashserv/server.py        |  4 ++--
 lib/layerindexlib/__init__.py |  1 -
 10 files changed, 35 insertions(+), 44 deletions(-)
 delete mode 100644 lib/bb/compat.py

-- 
2.25.1



             reply	other threads:[~2021-10-19 20:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 20:06 Steve Sakoman [this message]
2021-10-19 20:06 ` [bitbake][dunfell][1.46][PATCH 1/8] compat.py: remove file since it no longer actually implements anything Steve Sakoman
2021-10-19 20:06 ` [bitbake][dunfell][1.46][PATCH 2/8] bitbake: correct the collections vs collections.abc deprecation Steve Sakoman
2021-10-19 20:06 ` [bitbake][dunfell][1.46][PATCH 3/8] bitbake: fix regexp deprecation warnings Steve Sakoman
2021-10-19 20:06 ` [bitbake][dunfell][1.46][PATCH 4/8] bitbake: do not import imp in layerindexlib Steve Sakoman
2021-10-19 20:06 ` [bitbake][dunfell][1.46][PATCH 5/8] bitbake: adjust parser error check for python 3.10 compatibility Steve Sakoman
2021-10-19 20:06 ` [bitbake][dunfell][1.46][PATCH 6/8] bitbake: correct deprecation warning in process.py Steve Sakoman
2021-10-19 20:06 ` [bitbake][dunfell][1.46][PATCH 7/8] test/fetch: Update urls to match upstream branch name changes Steve Sakoman
2021-10-19 20:06 ` [bitbake][dunfell][1.46][PATCH 8/8] hashserv: let asyncio discover the running loop Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2020-07-15 14:26 [bitbake][dunfell][1.46][PATCH 0/8] Patch review Steve Sakoman

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.1634673786.git.steve@sakoman.com \
    --to=steve@sakoman.com \
    --cc=bitbake-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).