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][langdale][2.2][PATCH 0/1] Pull request (cover letter only)
Date: Wed, 23 Nov 2022 04:15:08 -1000	[thread overview]
Message-ID: <cover.1669212850.git.steve@sakoman.com> (raw)

The following changes since commit 138dd7883ee2c521900b29985b6d24a23d96563c:

  bitbake: bitbake-layers: checkout layer(s) branch when clone exists (2022-11-10 14:43:24 +0000)

are available in the Git repository at:

  https://git.openembedded.org/bitbake-contrib stable/2.2-next
  http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/2.2-next

Richard Purdie (1):
  runqueue: Fix race issues around hash equivalence and sstate reuse

 lib/bb/runqueue.py | 36 ++++++++++++++++++++----------------
 1 file changed, 20 insertions(+), 16 deletions(-)

-- 
2.25.1



             reply	other threads:[~2022-11-23 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 14:15 Steve Sakoman [this message]
2023-01-06 14:43 [bitbake][langdale][2.2][PATCH 0/1] Pull request (cover letter only) Steve Sakoman
2023-02-17 14:29 Steve Sakoman
2023-04-14 16:44 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.1669212850.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).