All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: paul.eggleton@linux.intel.com, clarson@kergoth.com,
	openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL 00/32] Ready for Final ACK & Pull
Date: Fri, 16 Aug 2013 11:08:51 +0100	[thread overview]
Message-ID: <1376647731.22952.114.camel@ted> (raw)
In-Reply-To: <cover.1376580529.git.sgw@linux.intel.com>

On Thu, 2013-08-15 at 08:32 -0700, Saul Wold wrote:
> Richard,
> 
> I updated this by removing the connman patch as suggested by Ross. I
> chose to leave in the Read-Only rootfs, as I have talked with Qi and
> I will have him send a follow on patch to fix the internal patch header.
> 
> I have tested the read-only stuff locally.
> 
> Thanks
> 	Sau!
> The following changes since commit 57662d4f813d5795cac1529633db80a09efdb089:
> 
>   meta-skeleton: Add busybox config fragment example (2013-08-13 23:03:44 +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
> 
> Chen Qi (14):
>   opkg.inc: remove the obsolete POSTLOG variable
>   makedevs: support using user/group names in device table files
>   image.bbclass: create device table after package installation
>   device_table-minimal.txt: use user/group names instead of uid/gid
>   init-live.sh: make $ROOT_MOUNT/media writable when necessary
>   use a uniform way to determine whether rootfs is read-only

I don't like the above patch since it spawns a ton of processes at boot
time. We can do better...

>   udev: remove implicit dependency on initscripts
>   populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR
>   populate-volatile.sh: don't spawn background process at rootfs time
>   runqemu-internal: fix to start X correctly in live images
>   initscripts: use a uniform way to handle directories in read-only
>     rootfs
>   populate-volatile.sh: use 'cp -a' to avoid potential problem
>   irda-utils: fix for read-only rootfs
>   openssh: fix for read-only rootfs
> 
> Cristiana Voicu (1):
>   systemtap: upgrade to 2.3
> 
> Martin Jansa (5):
>   at-spi2-core: add intltool-native dependency
>   gst-plugins-gl: add dependency on glew
>   xeyes: add dependency on libxrender
>   xrestop: add dependency on ncurses
>   qemu, default-providers: Add mesa as default virtual/egl
> 
> Muhammad Shakeel (3):
>   lighttpd: Replace spaces with tabs in shell function
>   rpcbind: Replace spaces with tabs in shell function
>   nfs-utils: Replace spaces with tabs in shell function
> 
> Otavio Salvador (1):
>   linux-dtb: Use kernel build system to generate the dtb files
> 
> Ross Burton (4):
>   cogl: GL/GLX feature cleanup
>   libmatchbox: upgrade to 1.11
>   matchbox-wm: fix icon handling on 64-bit hosts
>   wipe-sysroots: don't assume TMPDIR is under BUILDDIR
> 
> Saul Wold (2):
>   meta-skeleton: layer.conf Should also have .bbappend in example
>   texinfo: add perl RDEPENDS and fix up packaging
> 
> Stefan Herbrechtsmeier (1):
>   cmake.bbclass: Don't use packages from the native build machine
> 
> Wenzong Fan (1):
>   oe/path.py: call /bin/cp directly

Seriously? No. Add a sanity check and tell the user to fix their
environment if it will cause problems. There are a ton of other places
cp might fail have this issue, we're not hardcoding all of them.

Cheers,

Richard





      parent reply	other threads:[~2013-08-16 10:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 15:32 [CONSOLIDATED PULL 00/32] Ready for Final ACK & Pull Saul Wold
2013-08-15 15:39 ` Burton, Ross
2013-08-15 15:42 ` Paul Eggleton
2013-08-16 10:08 ` 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=1376647731.22952.114.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=clarson@kergoth.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --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.