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 11:09:26 +0100 [thread overview]
Message-ID: <5dca9bf84a4bd0265beead352beac6af9c0d4919.camel@linuxfoundation.org> (raw)
In-Reply-To: <AM6PR10MB3000B53772612F2BF2E835DB92A70@AM6PR10MB3000.EURPRD10.PROD.OUTLOOK.COM>
On Tue, 2020-05-05 at 08:13 +0000, Valek, Andrej wrote:
> I know, why the patch is failing, because of mixed line endings.
>
> I have already created a PR, where all patches fit as well. So you
> can take the patches from there instead of mailing list.
To be clear, I mean that I have a lot of requests from other people
about failing patches. There is a kernel reproducible builds issue, a
glib in meta-gplv2 issue, libinput, libacl-native and so on.
With yours I understand it needs to come from a git repo. You're using
github rather than poky-contrib so its not part of my normal workflow
and I personally hate the github UI to review a patch.
My point being I'll get to it but I'm struggling to keep up with the
problems with the patches already in master-next and that having
something outside "normal" just makes things harder and much as I wish
otherwise, lower down the queue.
Anyhow, I've added it locally so it will make the next round of testing
as its easier to "sort this" than discuss it.
Cheers,
Richard
prev parent reply other threads:[~2020-05-05 10:09 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
2020-05-05 8:13 ` Andrej Valek
2020-05-05 10:09 ` Richard Purdie [this message]
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=5dca9bf84a4bd0265beead352beac6af9c0d4919.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