From: "Paul Eggleton" <bluelightning@bluelightning.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Paul Eggleton <paul.eggleton@microsoft.com>,
Ross Burton <ross@burtonini.com>
Subject: Re: [OE-core] [PATCH] Revert "classes/buildhistory: also save recipe info for native recipes"
Date: Sat, 24 Oct 2020 00:09:20 +1300 [thread overview]
Message-ID: <35634030.XM6RcZxFsP@linc> (raw)
In-Reply-To: <CAAnfSTvDNN3wLpovsuJa8iDDJk_A6jsE2Ff3Zc3W8KaGKWNHBQ@mail.gmail.com>
On Friday, 23 October 2020 23:47:38 NZDT Ross Burton wrote:
> Verified this fixes my build failures.
>
> Ross
My apologies, this was not properly thought out nor sufficiently tested.
Paul
prev parent reply other threads:[~2020-10-23 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 10:46 [PATCH] Revert "classes/buildhistory: also save recipe info for native recipes" Richard Purdie
2020-10-23 10:47 ` [OE-core] " Ross Burton
2020-10-23 11:09 ` Paul Eggleton [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=35634030.XM6RcZxFsP@linc \
--to=bluelightning@bluelightning.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@microsoft.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross@burtonini.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