From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Frederic Martinsons <frederic.martinsons@gmail.com>
Cc: Martin Jansa <martin.jansa@gmail.com>,
Alex Kiernan <alex.kiernan@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH V5 6/6] cargo-update-recipe-crates: don't walk on the whole dir
Date: Mon, 03 Apr 2023 14:35:40 +0100 [thread overview]
Message-ID: <d5e1d50d126eadd0530c0513bc0b0f4c062c819b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+cAkeonKef=fqSLAMh_0+KhbAH96CYUHPh1=AJY6c3J6UhZ0Q@mail.gmail.com>
On Sat, 2023-04-01 at 17:21 +0200, Frederic Martinsons wrote:
> Hello, I just submitted a patch inside the bitbake fetcher to display
> all the missing checksum at once instead of only one.
>
> For the moment, I have no better solution, let's see what bitbake
> folks tell us about that.
I'm fine with that FWIW...
Cheers,
Richard
next prev parent reply other threads:[~2023-04-03 13:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 15:44 [PATCH V5 0/6] Extend cargo based recipe support frederic.martinsons
2023-03-30 15:44 ` [PATCH V5 1/6] cargo_common.bbclass: Support local github repos frederic.martinsons
2023-03-30 15:44 ` [PATCH V5 2/6] cargo_common.bbclass: add support of user in url for patch frederic.martinsons
2023-03-30 15:44 ` [PATCH V5 3/6] devtool: add support for multiple git url inside a cargo based recipe frederic.martinsons
2023-03-30 15:44 ` [PATCH V5 4/6] patch: support of git patches when the source uri contained subpath parameter frederic.martinsons
2023-03-30 15:44 ` [PATCH V5 5/6] meta-selftest: provide a recipe for zvariant frederic.martinsons
2023-03-30 15:44 ` [PATCH V5 6/6] cargo-update-recipe-crates: don't walk on the whole dir frederic.martinsons
2023-03-30 16:34 ` Alex Kiernan
2023-03-30 17:09 ` Frédéric Martinsons
[not found] ` <1751418A85B52050.27612@lists.openembedded.org>
2023-03-30 18:53 ` [OE-core] " Frédéric Martinsons
2023-03-30 19:23 ` Martin Jansa
2023-03-30 19:50 ` Frédéric Martinsons
2023-03-30 20:07 ` Frédéric Martinsons
2023-03-30 20:22 ` Martin Jansa
[not found] ` <17514C0A502D4FD8.27612@lists.openembedded.org>
2023-03-30 21:15 ` Martin Jansa
2023-03-31 5:32 ` Frédéric Martinsons
[not found] ` <17516A1097F71BFB.12651@lists.openembedded.org>
2023-04-01 15:21 ` Frédéric Martinsons
2023-04-03 13:35 ` Richard Purdie [this message]
2023-04-03 14:25 ` Frédéric Martinsons
2023-03-30 20:08 ` Martin Jansa
2023-03-30 20:20 ` Alex Kiernan
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=d5e1d50d126eadd0530c0513bc0b0f4c062c819b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kiernan@gmail.com \
--cc=frederic.martinsons@gmail.com \
--cc=martin.jansa@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