All of lore.kernel.org
 help / color / mirror / Atom feed
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/3] Fixes for self-hosted-image v3
Date: Thu, 05 Apr 2012 20:19:32 -0700	[thread overview]
Message-ID: <4F7E60C4.1000609@linux.intel.com> (raw)
In-Reply-To: <cover.1333648154.git.paul.eggleton@linux.intel.com>

On 04/05/2012 10:51 AM, Paul Eggleton wrote:
> Rebase my earlier patch and add a fix for Yocto bug #2208. Note that I
> have included Dexuan's fix for the sudoers file path to avoid conflicts.
>
>
> The following changes since commit 3e4562500956550dbae5467a5fe9289f1d32f775:
>
>    self-hosted-image: Increase space for build and allow builder user sudo access (2012-04-04 17:17:11 +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
>
> Dexuan Cui (1):
>    self-hosted-image: use the correct location of the file sudoers
>
> Paul Eggleton (2):
>    self-hosted-image: decrease reserved space to 0.5%
>    self-hosted-image: use Clearlooks theme
>
>   meta/recipes-core/images/self-hosted-image.bb |   13 +++++++++++--
>   meta/recipes-core/tasks/task-self-hosted.bb   |    3 ++-
>   2 files changed, 13 insertions(+), 3 deletions(-)
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-04-06  3:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 17:51 [PATCH 0/3] Fixes for self-hosted-image v3 Paul Eggleton
2012-04-05 17:51 ` [PATCH 1/3] self-hosted-image: use the correct location of the file sudoers Paul Eggleton
2012-04-05 17:51 ` [PATCH 2/3] self-hosted-image: decrease reserved space to 0.5% Paul Eggleton
2012-04-05 17:51 ` [PATCH 3/3] self-hosted-image: use Clearlooks theme Paul Eggleton
2012-04-06  3:19 ` 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=4F7E60C4.1000609@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.