All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Nyström" <david.c.nystrom@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/69] master-next & MUT (post M3)
Date: Mon, 04 Feb 2013 16:11:40 +0100	[thread overview]
Message-ID: <510FCFAC.4050909@gmail.com> (raw)
In-Reply-To: <cover.1359706204.git.sgw@linux.intel.com>

On 02/01/2013 09:19 AM, Saul Wold wrote:
> Richard,
>
> Here is a group of M4 patches and updates that have been
> pending. I fixed a small issue I found with the package.bbclass
> changes in gkt-icon-cache.bbclass
>
> I have included the DEB Incremental image set along with
> the READ-Only Rootfs changes, this way they can get broader
> views and usage by the community.
>
> I have also include the GCC Multilib changes.
>
> I just started the AB on MUT without some failing patches
> (netbase and flex).
>
> Please watch it's status, There was a failure in the x86 GRUB
> build which may also point back to Flex.
>
> Sau!
>
> This include
> The following changes since commit 1489a69cecb1dcc3502a4c24beaea81e6ca6dacc:
>
>    harfbuzz: fix install of version.h (2013-01-31 12:29:18 +0000)
>
> are available in the git repository at:
>
>    git://git.openembedded.org/openembedded-core-contrib sgw/stage
>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/stage
>
>
> David Nyström (1):
>    Lets face it, adding python dependencies is really a painful manual
>      process, due to setuptools/distutils, ignoring anything other than
>      python dependencies.


Please drop above as well, it was an RFC meant to stir up some 
discussion, not meant for inclusion.





  parent reply	other threads:[~2013-02-04 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01  8:19 [CONSOLIDATED PULL 00/69] master-next & MUT (post M3) Saul Wold
2013-02-01 10:18 ` Martin Jansa
2013-02-04 15:11 ` David Nyström [this message]
2013-02-04 16:16   ` 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=510FCFAC.4050909@gmail.com \
    --to=david.c.nystrom@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.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 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.