From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Valek, Andrej" <andrej.valek@siemens.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>
Subject: Re: [OE-core][PATCH] icu: upgrade 66.1 -> 67.1
Date: Tue, 05 May 2020 09:11:20 +0100 [thread overview]
Message-ID: <abf15032d9b14a18031f0c017ab422365d386930.camel@linuxfoundation.org> (raw)
In-Reply-To: <AM6PR10MB30002791F30A5942D6CB496592A70@AM6PR10MB3000.EURPRD10.PROD.OUTLOOK.COM>
On Tue, 2020-05-05 at 07:56 +0000, Valek, Andrej wrote:
> Hello Richard,
>
> Could you please take a look on it?
I will. Keep in mind that I've multiple people asking me to help
understand why their patches fail in testing and I can only deal with
so many at once. As soon as something needs extra work like this does,
it makes it harder to get around to.
Cheers,
Richard
next prev parent reply other threads:[~2020-05-05 8:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 8:26 [OE-core][PATCH] icu: upgrade 66.1 -> 67.1 Andrej Valek
2020-05-01 8:32 ` ✗ patchtest: failure for " Patchwork
2020-05-01 8:45 ` [OE-core][PATCH v2] " Andrej Valek
2020-05-01 9:02 ` ✗ patchtest: failure for icu: upgrade 66.1 -> 67.1 (rev2) Patchwork
2020-05-01 11:39 ` [OE-core][PATCH v3] icu: upgrade 66.1 -> 67.1 Andrej Valek
2020-05-05 15:00 ` Richard Purdie
2020-05-05 19:26 ` Alexander Kanavin
2020-05-07 5:05 ` Khem Raj
2020-05-01 12:02 ` ✗ patchtest: failure for icu: upgrade 66.1 -> 67.1 (rev3) Patchwork
2020-05-01 13:48 ` [OE-core][PATCH] icu: upgrade 66.1 -> 67.1 Andrej Valek
2020-05-01 13:56 ` Alexander Kanavin
2020-05-01 16:52 ` Andrej Valek
2020-05-01 22:16 ` Alexander Kanavin
2020-05-02 17:28 ` Andrej Valek
2020-05-05 7:56 ` Andrej Valek
2020-05-05 8:11 ` Richard Purdie [this message]
2020-05-05 8:13 ` Andrej Valek
2020-05-05 10:09 ` Richard Purdie
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=abf15032d9b14a18031f0c017ab422365d386930.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=andrej.valek@siemens.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