All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: yocto@yoctoproject.org
Subject: Re: is yocto based on oe-core *as-is*?
Date: Sun, 11 Mar 2012 22:38:13 +0000	[thread overview]
Message-ID: <1503814.Y6Q9bri6nF@helios> (raw)
In-Reply-To: <4F5C9E99.5010509@mlbassoc.com>

On Sunday 11 March 2012 06:46:17 Gary Thomas wrote:
> On 2012-03-11 06:33, Paul Eggleton wrote:
> > This is correct, and you can verify it by doing a diff of the OE-Core
> > meta/
> > subdirectory against Poky's meta/ - the only difference is that Poky does
> > not include the sample configs (it provides its own in meta-yocto).
> 
> Have you actually done such a comparison? 

Yes, I did so before sending the above message.

> I just compared them like this:
>    poky/yocto:
>       commit 320558f494c618f53e0c773db3ea0109476e8359
>       Author: Paul Eggleton <paul.eggleton@linux.intel.com>
>       Date:   Wed Feb 29 12:59:14 2012 +0000
> 
>    openembedded-core:
>       commit 50dc8bfbac42b9a9b52a2f7d0568740c41790c13
>       Author: Richard Purdie <richard.purdie@linuxfoundation.org>
>       Date:   Fri Mar 9 14:14:04 2012 +0800
> 
> These are the up-to-date master branches, as of 2012-03-11 12:40 GMT

I don't think you'll find they are. Your poky branch is behind OE-Core by quite 
a number of commits - in fact 320558f494c618f53e0c773db3ea0109476e8359 is 
where the 1.2_M3 branch HEAD is currently, are you sure you aren't on that 
branch instead of master?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2012-03-11 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10  9:40 is yocto based on oe-core *as-is*? Robert P. J. Day
2012-03-11 12:33 ` Paul Eggleton
2012-03-11 12:46   ` Gary Thomas
2012-03-11 22:38     ` Paul Eggleton [this message]
2012-03-12 10:25       ` Gary Thomas

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=1503814.Y6Q9bri6nF@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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.