Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Upgrade opkg
Date: Tue, 17 May 2011 11:29:37 -0700	[thread overview]
Message-ID: <4DD2BE91.1090406@intel.com> (raw)
In-Reply-To: <cover.1305442428.git.raj.khem@gmail.com>

On 05/14/2011 11:57 PM, Khem Raj wrote:
> These patches help in removing extra size that was being added to
> slugos-image when using oe-core. With these patches both from OE
> the root file system is 100k less than the classic OE. Currently
> the root file size is about 1M bigger due to opkg pulling in curl
> and then bunch of other libraries
>
> Pull URL: git://git.openembedded.org/openembedded-core-contrib
>    Branch: kraj/slugos-support
>    Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/slugos-support
>
> Thanks,
>      Khem Raj<raj.khem@gmail.com>
> ---
>
>
> Khem Raj (2):
>    opkg: Bump SRCREV to 609
>    e2fsprogs_1.41.14.bb: Package libraries into separate packages
>
>   .../e2fsprogs/e2fsprogs_1.41.14.bb                 |    6 ++++++
>   meta/recipes-devtools/opkg/opkg.inc                |    8 ++++++--
>   meta/recipes-devtools/opkg/opkg_svn.bb             |    3 ++-
>   3 files changed, 14 insertions(+), 3 deletions(-)
>
Merged into oe-core

Thanks
	Sau!




      parent reply	other threads:[~2011-05-17 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15  6:57 [PATCH 0/2] Upgrade opkg Khem Raj
2011-05-15  6:57 ` [PATCH 1/2] opkg: Bump SRCREV to 609 Khem Raj
2011-05-15  6:57 ` [PATCH 2/2] e2fsprogs_1.41.14.bb: Package libraries into separate packages Khem Raj
2011-05-17 18:29 ` Saul Wold [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=4DD2BE91.1090406@intel.com \
    --to=saul.wold@intel.com \
    --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