From: Phil Blundell <pb@pbcl.net>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] rm_work.bbclass: inhibit rm_work per recipe
Date: Tue, 09 Apr 2013 22:01:05 +0100 [thread overview]
Message-ID: <1365541265.2116.9.camel@pb-ThinkPad-R50e> (raw)
In-Reply-To: <6500457.3vgtoKXQDv@helios>
On Tue, 2013-03-26 at 17:52 +0000, Paul Eggleton wrote:
> I'm sure this has come up before, but is rm_old_work something we ought to
> have in OE-Core?
Obviously it's not for me to say, but I suspect probably not. It
requires ${WORKDIR} to follow a particular pattern, which not everybody
will necessarily want, and I don't think you could really argue that it
represents "core" functionality either.
p.
next prev parent reply other threads:[~2013-04-09 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 7:01 [PATCH 0/1] rm_work.bbclass: inhibit rm_work per recipe Qi.Chen
2013-03-13 7:01 ` [PATCH 1/1] " Qi.Chen
2013-03-26 17:12 ` Paul Eggleton
2013-03-26 17:15 ` Burton, Ross
2013-03-26 17:25 ` Phil Blundell
2013-03-26 17:52 ` Paul Eggleton
2013-04-09 21:01 ` Phil Blundell [this message]
2013-04-09 22:55 ` Martin Jansa
2013-03-26 17:55 ` Martin Jansa
2013-03-26 18:02 ` Paul Eggleton
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=1365541265.2116.9.camel@pb-ThinkPad-R50e \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@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.