From: Tom Rini <tom.rini@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [2011.03-maintenance][PATCH 0/9] Pull request 20120719
Date: Mon, 30 Jul 2012 14:08:27 -0700 [thread overview]
Message-ID: <20120730210827.GE9554@bill-the-cat> (raw)
In-Reply-To: <cover.1342677797.git.apelete@seketeli.net>
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
On Thu, Jul 19, 2012 at 07:20:31PM +0200, Apelete Seketeli wrote:
> Hello,
>
> The patches that come as a follow-up of this message fix issues found
> while building muffinman-image on top of the 2011.03-maintenance
> branch.
> These modifications were tested by successfully building
> muffinman-image from scratch on a Debian Squeeze host.
> Please pull into 2011.03-maintenance branch.
>
> The following changes since commit f9611c025109a3e0d6cebf12f49ae24c97759c09:
>
> psplash: convert from svn.o-hand.com to git.yoctoproject.org (2012-07-04 22:34:04 +0200)
>
> are available in the git repository at:
>
> git://seketeli.net/~apelete/oe.git muffinman-image-fix
>
> Apelete Seketeli (9):
> mirrors.bbclass: add new GNU_MIRROR
> mirrors.bbclass: add new KERNELORG_MIRROR
> libpng: update SRC_URI
> bluez4_4.84: update checksum values
> netsurf: update SRC_URI
> tzcode: update SRC_URI
> tzdata: update SRC_URI
> git: update SRC_URI
> opkg-utils: bump SRCREV to keep python2.6 compatibility
>
> classes/mirrors.bbclass | 2 ++
> recipes/bluez/bluez4_4.84.bb | 4 ++--
> recipes/git/git.inc | 2 +-
> recipes/libpng/libpng.inc | 2 +-
> recipes/netsurf/hubbub_0.0.2.bb | 2 +-
> recipes/netsurf/libcss_0.0.2.bb | 2 +-
> recipes/netsurf/libnsbmp_0.0.2.bb | 2 +-
> recipes/netsurf/libnsgif_0.0.2.bb | 2 +-
> recipes/netsurf/libparserutils_0.0.2.bb | 2 +-
> recipes/netsurf/libwapcaplet_0.0.2.bb | 2 +-
> recipes/netsurf/netsurf_2.6.bb | 2 +-
> recipes/opkg-utils/opkg-utils_git.bb | 4 ++--
> recipes/tzcode/tzcode-native.inc | 4 ++--
> recipes/tzdata/tzdata.inc | 2 +-
> 14 files changed, 18 insertions(+), 16 deletions(-)
Applied, thanks.
--
Tom
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2012-07-30 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 17:20 [2011.03-maintenance][PATCH 0/9] Pull request 20120719 Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 1/9] mirrors.bbclass: add new GNU_MIRROR Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 2/9] mirrors.bbclass: add new KERNELORG_MIRROR Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 3/9] libpng: update SRC_URI Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 4/9] bluez4_4.84: update checksum values Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 5/9] netsurf: update SRC_URI Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 6/9] tzcode: " Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 7/9] tzdata: " Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 8/9] git: " Apelete Seketeli
2012-07-19 17:20 ` [2011.03-maintenance][PATCH 9/9] opkg-utils: bump SRCREV to keep python2.6 compatibility Apelete Seketeli
2012-07-23 19:48 ` [2011.03-maintenance][PATCH 0/9] Pull request 20120719 Tom Rini
2012-07-23 20:33 ` Apelete Seketeli
2012-07-30 21:07 ` Tom Rini
2012-07-30 19:09 ` Apelete Seketeli
2012-07-30 21:08 ` Tom Rini [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=20120730210827.GE9554@bill-the-cat \
--to=tom.rini@gmail.com \
--cc=openembedded-devel@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 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.