From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] parse/ast: Expand inherit statements before splitting them
Date: Thu, 08 Mar 2012 07:01:57 -0800 [thread overview]
Message-ID: <1331218917.3006.0.camel@ted> (raw)
In-Reply-To: <CAEsOVNfV1iy1Npks-3fuT0g+sLXenNMc8+n_mAV-t9RX6AtcSQ@mail.gmail.com>
On Wed, 2012-03-07 at 22:13 +0000, McClintock Matthew-B29882 wrote:
> On Sat, Mar 3, 2012 at 10:17 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > This means that statements that expand to more then one entry
> > such as:
> >
> > CLASSES = "a b"
> > inherit ${CLASSES}
> >
> > work correctly instead of trying to inherit a class called "a b".
>
> Does this effect:
>
> CLASSES = ""
>
> inherit a ${CLASSES}
Possibly in that if it didn't work before, it perhaps does now. I
certainly can't see the change making this any less functional.
Cheers,
Richard
prev parent reply other threads:[~2012-03-08 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 4:17 [PATCH] parse/ast: Expand inherit statements before splitting them Richard Purdie
2012-03-07 22:13 ` McClintock Matthew-B29882
2012-03-08 15:01 ` 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=1331218917.3006.0.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B29882@freescale.com \
--cc=bitbake-devel@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