From: Mike Crowe <mac@mcrowe.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2] cmake: Avoid passing empty prefix to os.path.relpath
Date: Sat, 6 Jan 2018 20:16:18 +0000 [thread overview]
Message-ID: <20180106201618.ktj64aparfs47yjv@mcrowe.com> (raw)
In-Reply-To: <20171220102822.4ohufxtgcu3lg3r5@mcrowe.com>
https://patchwork.openembedded.org/patch/145709/
On Wednesday 20 December 2017 at 10:28:22 +0000, Mike Crowe wrote:
> On Monday 11 December 2017 at 13:45:26 +0000, Burton, Ross wrote:
> > It was implicated in some build failures. I'll re-add it and try again.
>
> Thanks. Are the new results in? I had a poke about on autobuilder.yocto.io
> but couldn't work out how to tell which builds this commit was included in.
> Build 719 did not appear to include it.
Any more news?
Thanks.
Mike.
next prev parent reply other threads:[~2018-01-06 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 16:39 [PATCHv2] cmake: Avoid passing empty prefix to os.path.relpath Mike Crowe
2017-11-13 17:15 ` Otavio Salvador
2017-12-11 9:51 ` Mike Crowe
2017-12-11 13:45 ` Burton, Ross
2017-12-20 10:28 ` Mike Crowe
2018-01-06 20:16 ` Mike Crowe [this message]
2019-06-11 13:58 ` Mike Crowe
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=20180106201618.ktj64aparfs47yjv@mcrowe.com \
--to=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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