Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] v2 Self-Hosted Image patches
Date: Tue, 17 Apr 2012 15:02:10 -0700	[thread overview]
Message-ID: <cover.1334700068.git.sgw@linux.intel.com> (raw)

Richard,

This set of changes adds the lsb_release command and 
sets the i/etc/lsb-release file up correctly for the 
release.

I also am removing the BB_NO_NETWORK from the self-hosted
image to allow it to have network, and updating the SRCREV,
which you might have to do again to get these patches actaully 
into the image.

V2: better commit messages

Thanks
	Sau!

The following changes since commit 89788fbd10fdfbbe54927339d7ec516d0e4d7ef5:

  libproxy: Allow to build in non-gplv3 configuration (2012-04-17 14:08:27 +0100)

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

Saul Wold (3):
  lsb: Add DISTRO Info to /etc/lsb-release file also add util-linux to
    DEPENDS
  task-self-hosted: Add LSB for distro info
  self-hosted-image: remove BB_NO_NETWORK and update Poky SRCREV

 meta/recipes-core/images/self-hosted-image.bb |    5 ++---
 meta/recipes-core/tasks/task-self-hosted.bb   |    1 +
 meta/recipes-extended/lsb/lsb_1.4.bb          |    5 +++++
 3 files changed, 8 insertions(+), 3 deletions(-)

-- 
1.7.7.6




             reply	other threads:[~2012-04-17 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 22:02 Saul Wold [this message]
2012-04-17 22:02 ` [PATCH 1/3] lsb: Add DISTRO Info to /etc/lsb-release file also add util-linux to DEPENDS Saul Wold
2012-04-17 22:02 ` [PATCH 2/3] task-self-hosted: Add LSB for distro info Saul Wold
2012-04-17 22:02 ` [PATCH 3/3] self-hosted-image: remove BB_NO_NETWORK and update Poky SRCREV Saul Wold
2012-04-18  6:46 ` [PATCH 0/3] v2 Self-Hosted Image patches Koen Kooi

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=cover.1334700068.git.sgw@linux.intel.com \
    --to=sgw@linux.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