From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][dunfell][1.46][PATCH 0/1] Pull request (cover letter only)
Date: Mon, 24 Jan 2022 12:35:25 -1000 [thread overview]
Message-ID: <cover.1643063657.git.steve@sakoman.com> (raw)
The following changes since commit e6d75e0beb95aa0cdf82bbc0a6b767c7f6cfcfc0:
tests/fetch: Drop gnu urls from wget connectivity test (2022-01-17 21:53:02 +0000)
are available in the Git repository at:
git://git.openembedded.org/bitbake-contrib stable/1.46-next
http://cgit.openembedded.org/bitbake-contrib/log/?h=stable/1.46-next
Jate Sujjavanich (1):
hashserv: specify loop for asyncio in python < 3.6
lib/hashserv/server.py | 23 +++++++++++++++++------
1 file changed, 17 insertions(+), 6 deletions(-)
--
2.25.1
next reply other threads:[~2022-01-24 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 22:35 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-30 17:27 [bitbake][dunfell][1.46][PATCH 0/1] Pull request (cover letter only) Steve Sakoman
2022-08-21 23:06 Steve Sakoman
2022-04-04 14:18 Steve Sakoman
2021-05-18 14:14 Steve Sakoman
2021-02-18 14:37 Steve Sakoman
2020-12-01 14:14 Steve Sakoman
2020-09-18 16:11 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.1643063657.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