Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] staging: Avoid staging the same binaries again and again
Date: Fri, 28 Sep 2012 11:43:31 +0100	[thread overview]
Message-ID: <1348829012.32611.41.camel@phil-desktop> (raw)
In-Reply-To: <1348781754.15753.21.camel@ted>

On Thu, 2012-09-27 at 22:35 +0100, Richard Purdie wrote:
> The release is now at -rc2 and this patch hasn't reached the threshold
> of things I'm willing to take. I've tried to at least get some of the
> patches you're posted in but I wish we'd had them a couple of weeks
> ago :/.

Okay, fair enough.  There's no particular rush with any of that stuff
and it can perfectly well wait until your release is out of the way.  Do
you want me to resend those patches at some later date?

You might like to consider taking the eglibc patch from a few days ago
since it is arguably a regression that eglibc has a build dependency on
perl when it didn't use to.  But of course this may not matter for the
majority of yocto users so it might not be a problem in practice.

p.





      reply	other threads:[~2012-09-28 10:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24  6:26 [PATCH] staging: Avoid staging the same binaries again and again Phil Blundell
2012-09-24  8:51 ` Richard Purdie
2012-09-24  9:40   ` Phil Blundell
2012-09-24  9:54     ` Richard Purdie
2012-09-24  9:59       ` Phil Blundell
2012-09-27 21:18       ` Phil Blundell
2012-09-27 21:35         ` Richard Purdie
2012-09-28 10:43           ` Phil Blundell [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=1348829012.32611.41.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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