From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 0/2] Fix for self-hosted-image
Date: Wed, 04 Apr 2012 08:46:15 -0700 [thread overview]
Message-ID: <4F7C6CC7.6010305@linux.intel.com> (raw)
In-Reply-To: <cover.1333553396.git.paul.eggleton@linux.intel.com>
On 04/04/2012 08:32 AM, Paul Eggleton wrote:
> Allow additional options when running tune2fs -j on ext3 images and use
> that to specify -m 0.5 for self-hosted-image.
>
> Note these patches should be applied on top of Saul's recent
> self-hosted-image patch once that is merged.
>
> The following changes since commit 7c794db563cc35f6deaab1dd0fef35015d47e567:
>
> self-hosted-image: Increase space for build and allow builder user sudo access (2012-04-04 16:16:27 +0100)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib paule/self
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/self
>
> Paul Eggleton (2):
> classes/image_types: add IMAGE_TUNE2FS_ext3
> self-hosted-image: decrease reserved space to 0.5%
>
> meta/classes/image_types.bbclass | 4 +++-
> meta/recipes-core/images/self-hosted-image.bb | 4 +++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
Acked-by: Saul Wold <sgw@linux.intel.com>
prev parent reply other threads:[~2012-04-04 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 15:32 [PATCH 0/2] Fix for self-hosted-image Paul Eggleton
2012-04-04 15:32 ` [PATCH 1/2] classes/image_types: add IMAGE_TUNE2FS_ext3 Paul Eggleton
2012-04-04 16:57 ` Otavio Salvador
2012-04-04 17:12 ` Paul Eggleton
2012-04-04 17:26 ` Otavio Salvador
2012-04-04 19:30 ` Paul Eggleton
2012-04-04 15:32 ` [PATCH 2/2] self-hosted-image: decrease reserved space to 0.5% Paul Eggleton
2012-04-04 16:58 ` Otavio Salvador
2012-04-04 15:46 ` 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=4F7C6CC7.6010305@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@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.