From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/50] automake, read-only, mutlilib, and updates
Date: Wed, 16 Jan 2013 12:11:19 +0000 [thread overview]
Message-ID: <1358338279.8129.8.camel@ted> (raw)
In-Reply-To: <cover.1358322515.git.sgw@linux.intel.com>
On Tue, 2013-01-15 at 23:56 -0800, Saul Wold wrote:
> The following changes since commit 6080d1dc719c38fd97c2abd38e0ad938fbf6f452:
>
> connman: fixed init script so connman can runs over nfs (2013-01-15 08:09:30 +0000)
>
> 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
>
> Andrei Dinu (1):
> Removed undisplayed picture from connman-gnome
>
> Chen Qi (7):
> runqemu scripts: add support for booting an ISO image
> sysvinit: add ROOTFS_READ_ONLY variable to rcS-default
> image.bbclass: add a hook funtion to support readonly rootfs
> core-image.bbclass: support read-only rootfs
> initscripts: support read-only rootfs
> volatile-conf-minimal: add recipe
> volatile-conf-sato: add recipe
This ro-rootfs stuff is setting off warnings in my mind, I need to look
at the patches more to figure out why. I therefore didn't take the
patches for now.
> Constantin Musca (5):
> gcc: remove the 64bithack patch
> multilib.conf: add TARGET_ARCH to MULTILIB_SAVE_VARNAME
> gcc: enable multilib for target gcc
> tune-mips32: add BASE_LIB to mips32 tunes
> tune-ppc603e: add BASE_LIB
Again, something isn't quite right here, haven't figured out what yet.
> Cristian Iorga (6):
> db: upgrade to 5.3.21
> iproute2: upgrade to v3.7.0
> quota: upgrade to 4.01
> qemu: machine override ability added
> connman-conf: configures connman in qemu machines
> connman: upgrade to 1.10
>
> Emilia Ciobanu (1):
> distrodata: Updated checkpkg task
>
> Eric Bénard (1):
> add meta-toolchain-qt
>
> Jesse Zhang (1):
> coreutils: remove dependency on coreutils-native
I've replied to this one, not taken.
> Marko Lindqvist (21):
> polkit: replace obsolete automake macros with working ones
> pango: replace obsolete automake macros with working ones
> libxsettings-client: replace obsolete automake macros with working
> ones
> rgb: replace obsolete automake macros with working ones
> sysfsutils: replace obsolete automake macros with working ones
> vte: replace obsolete automake macros with working ones
> libtirpc: replace obsolete automake macros with working ones
> curl: fix build with automake-1.13
> bluez-hcidump: replace obsolete automake macros with working ones
> alsa-utils: replace obsolete automake macros with working ones
> tremor: replace obsolete automake macros with working ones
> ofono: replace obsolete automake macros with working ones
> libidn: add checksums to version 0.6.14 recipe
> gzip: fix license segment md5sum boundary
> iptables: fix license segment md5sum boundary
> shadow: fix license segment md5sum boundary
> ethtool: fix license segment md5sum boundary
> gperf: fix license segment md5sum boundary
> libidn: fix license segment md5sum boundary
> dbus: fix license segment md5sum boundary
> apmd: fix license segment md5sum boundary
>
> Muhammad Shakeel (2):
> archiver class: Use tasks with sstate instead of pre/post funcs
> archive-*-source.bbclass: Handle all package classes
Replied to these with feedback. They're using "internal" bitbake API and
don't need to.
> Robert P. J. Day (1):
> image_types.bbclass: Add and update comments regarding image types.
>
> Saul Wold (1):
> xz: LICENSE field is wrong
>
> Tom Zanussi (3):
> lttng: remove 'legacy' lttng
> lttng2-ust: rename to lttng-ust
> recipes-kernel/lttng-2.0: rename to recipes-kernel/lttng
I took everything else.
Cheers,
Richard
prev parent reply other threads:[~2013-01-16 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 7:56 [CONSOLIDATED PULL 00/50] automake, read-only, mutlilib, and updates Saul Wold
2013-01-16 12:11 ` Richard Purdie [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=1358338279.8129.8.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@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.