From: Peter Seebach <peter.seebach@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: CONFLICTS as keyword or just misspelled RCONFLICTS?
Date: Tue, 8 May 2012 14:25:58 -0500 [thread overview]
Message-ID: <20120508142558.5837dc31@wrlaptop> (raw)
In-Reply-To: <4FA971F0.8020406@windriver.com>
On Tue, 8 May 2012 14:20:16 -0500
Mark Hatle <mark.hatle@windriver.com> wrote:
> > BTW: IIRC TUNE_CONFLICTS/TUNECONFLICTS inconsistency was discussed
> > on ML already (I could not find that thread, but still it's used in
> > meta/conf/machine/include/arm
>
> Ya, patches to fix these, and actually check them were sent to the
> list, but I don't believe they have been merged yet.
I hadn't noticed TUNE_CONFLICTS, just TUNECONFLICT and TUNECONFLICTS.
As of this writing, I have two outstanding patches to do with that; I
think the consistency patch is in, but we're still waiting on
approval/more changes decisions on the sanity check implementation.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2012-05-08 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 18:02 CONFLICTS as keyword or just misspelled RCONFLICTS? Martin Jansa
2012-05-08 19:20 ` Mark Hatle
2012-05-08 19:25 ` Peter Seebach [this message]
2012-06-16 6:51 ` Martin Jansa
2012-07-07 8:31 ` [PATCH] conf/machine: replace TUNE_CONFLICTS with TUNECONFLICTS Martin Jansa
2012-07-17 15:09 ` Saul Wold
2012-06-16 18:08 ` [PATCH 1/2] recipes: replace CONFLICTS with RCONFLICTS_${PN} Martin Jansa
2012-06-16 18:08 ` [PATCH 2/2] tzdata, matchbox-session, mini-x-session: replace RCONFLICTS with RCONFLICTS_ Martin Jansa
2012-06-18 12:42 ` [PATCH 1/2] recipes: replace CONFLICTS with RCONFLICTS_${PN} Richard Purdie
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=20120508142558.5837dc31@wrlaptop \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox