Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Yoann Congal <yoann.congal@smile.fr>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][wrynose][2.18][PATCH 0/2] Patch review
Date: Fri, 17 Jul 2026 11:52:14 +0200	[thread overview]
Message-ID: <cover.1784281828.git.yoann.congal@smile.fr> (raw)

Please review this set of changes for wrynose/2.18 and have comments back by
end of day Tuesday, July 21.

Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4214

The following changes since commit acfe02fa38b5da9e6a36c6cedcf91d4fcbefbfbd:

  tests/fetch: cover checkstatus redirect auth handling (2026-06-11 11:50:29 +0200)

are available in the Git repository at:

  https://git.openembedded.org/bitbake-contrib stable/2.18-nut
  https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.18-nut

for you to fetch changes up to fae9db3168dbff1b8c76fe9c6726a9687ff97514:

  utils: Add NFS EEXISTS/isdir failure workaround (2026-07-09 17:37:07 +0200)

----------------------------------------------------------------

Ernest Van Hoecke (1):
  bitbake-setup: always write newline at end of the README

Richard Purdie (1):
  utils: Add NFS EEXISTS/isdir failure workaround

 bin/bitbake-setup |  5 +++--
 lib/bb/utils.py   | 14 +++++++++++++-
 2 files changed, 16 insertions(+), 3 deletions(-)



             reply	other threads:[~2026-07-17  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  9:52 Yoann Congal [this message]
2026-07-17  9:52 ` [bitbake][wrynose][2.18][PATCH 1/2] bitbake-setup: always write newline at end of the README Yoann Congal
2026-07-17  9:52 ` [bitbake][wrynose][2.18][PATCH 2/2] utils: Add NFS EEXISTS/isdir failure workaround Yoann Congal

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.1784281828.git.yoann.congal@smile.fr \
    --to=yoann.congal@smile.fr \
    --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