From: Adrian Bunk <bunk@stusta.de>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH V2] s-suite: push SRCREV to version 3.4
Date: Tue, 4 Jun 2019 11:37:55 +0300 [thread overview]
Message-ID: <20190604083755.GA2249@localhost> (raw)
In-Reply-To: <83FEA552-5A4B-4A54-BBF9-2D88B4B6B11F@linaro.org>
On Tue, Jun 04, 2019 at 09:38:48AM +0200, Paolo Valente wrote:
> Hi,
Hi Paolo,
> anyone had time to look into this? Is the patch ok now?
it looks OK to me.
The delay is caused by [1], so don't worry if it takes until next week
for a merge or reply from Khem.
> Thanks,
> Paolo
cu
Adrian
[1] http://lists.openembedded.org/pipermail/openembedded-devel/2019-May/199871.html
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-06-04 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 13:21 [meta-oe][PATCH V2] s-suite: push SRCREV to version 3.4 Paolo Valente
2019-06-04 7:38 ` Paolo Valente
2019-06-04 8:37 ` Adrian Bunk [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=20190604083755.GA2249@localhost \
--to=bunk@stusta.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paolo.valente@linaro.org \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.