From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] siteinfo.bbclass: Add powerpc-linux-gnuspe.
Date: Fri, 13 May 2011 11:45:59 +0100 [thread overview]
Message-ID: <1305283559.19606.42.camel@rex> (raw)
In-Reply-To: <BANLkTi=zwa4m050EcKkSp_KV8LOUYQK67g@mail.gmail.com>
On Fri, 2011-05-13 at 12:28 +0200, Leon Woestenberg wrote:
> Hello Khem,
>
> On Fri, May 13, 2011 at 5:50 AM, Khem Raj <raj.khem@gmail.com> wrote:
> > On Wed, May 11, 2011 at 3:29 AM, Leon Woestenberg
> > <leon.woestenberg@gmail.com> wrote:
> >> From: Leon Woestenberg <leon@sidebranch.com>
> >> Re-add powerpc-linux-gnuspe, from OpenEmbedded. Also adds support
> >> to poky.conf so that minimal-core-image builds with DISTRO=poky,
> >
> > you need to rebase this patch on latest oe-core
> >
> Yes, I was using oe-core-contrib/master as a base, wrongly assuming
> that that is the correct base for -contrib fixes/additions.
To be fair when you wrote the patch, the conflicting distro changes were
not in either branch so in that case it didn't matter.
It was easier to take the distro changes and fix this up than the other
way around though.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-13 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 10:29 [PATCH 0/1] Re-add powerpc-linux-gnuspe support Leon Woestenberg
2011-05-11 10:29 ` [PATCH 1/1] siteinfo.bbclass: Add powerpc-linux-gnuspe Leon Woestenberg
2011-05-13 3:50 ` Khem Raj
2011-05-13 9:26 ` Richard Purdie
2011-05-13 10:28 ` Leon Woestenberg
2011-05-13 10:45 ` Richard Purdie [this message]
2011-05-13 10:51 ` Leon Woestenberg
2011-05-11 15:04 ` [PATCH 0/1] Re-add powerpc-linux-gnuspe support 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=1305283559.19606.42.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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