Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] dexuan: more build appliance patches: [Apr 1, 2012]
Date: Mon, 02 Apr 2012 04:28:57 +0100	[thread overview]
Message-ID: <1333337337.647.3.camel@ted> (raw)
In-Reply-To: <cover.1333295122.git.dexuan.cui@intel.com>

On Mon, 2012-04-02 at 00:10 +0800, Dexuan Cui wrote:
> BTW:
> I added a "Upstream-Status: inappropriat" into every patches to genext2fs.
> 
> With the patches, I only spent about 10~15 minutes to create a 4.5GB
> .rootfs.ext3 file by genext2fs.
> 
> 
> The following changes since commit 8691a588267472eb5a32b978a0eb9ddfd0c91733:
> 
>   cross-canadian.bbclass: fix rpath for sdk executables (2012-03-31 18:00:59 +0100)
> 
> are available in the git repository at:
>   git://git.yoctoproject.org/poky-contrib dcui/master
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=dcui/master
> 
> Dexuan Cui (5):
>   genext2fs: support large files and  filesystems without using large
>     amounts of memory
>   self-hosted-image: improve do_populate_poky_src
>   self-hosted-image: renew the poky src's SRCREV that's installed into
>     the target
>   builder: uncomment the settings for BB_NUMBER_THREADS and
>     PARALLEL_MAKE
>   self-hosted-image: fix indentation: 8 spaces --> Tab

I've merged these to master, thanks. Whilst I'm reluctant to do so at
this point in the release process for such major changes, I think in
this case it does make sense since the genext2fs changes seem to fix a
number of problematic issues.

Cheers,

Richard




  parent reply	other threads:[~2012-04-02  3:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01 16:10 [PATCH 0/5] dexuan: more build appliance patches: [Apr 1, 2012] Dexuan Cui
2012-04-01 16:10 ` [PATCH 1/5] genext2fs: support large files and filesystems without using large amounts of memory Dexuan Cui
2012-04-02  2:26   ` Cui, Dexuan
2012-04-01 16:10 ` [PATCH 2/5] self-hosted-image: improve do_populate_poky_src Dexuan Cui
2012-04-01 16:10 ` [PATCH 3/5] self-hosted-image: renew the poky src's SRCREV that's installed into the target Dexuan Cui
2012-04-01 16:10 ` [PATCH 4/5] builder: uncomment the settings for BB_NUMBER_THREADS and PARALLEL_MAKE Dexuan Cui
2012-04-01 16:10 ` [PATCH 5/5] self-hosted-image: fix indentation: 8 spaces --> Tab Dexuan Cui
2012-04-02  3:28 ` Richard Purdie [this message]
2012-04-03 20:49   ` [PATCH 0/5] dexuan: more build appliance patches: [Apr 1, 2012] Koen Kooi
2012-04-05 17:21     ` Cui, Dexuan
2012-04-06 13:32       ` Koen Kooi
2012-04-06 13:43         ` Cui, Dexuan

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=1333337337.647.3.camel@ted \
    --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