From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/4] default-distrovars: Add empty weak definition for DISTRO variable
Date: Thu, 22 Mar 2012 17:52:02 +0000 [thread overview]
Message-ID: <1332438722.9740.290.camel@ted> (raw)
In-Reply-To: <CAMKF1soTe_6YB+eh_5YLojiAh9=bMP+hu4DUzi8SHSvABv0Nuw@mail.gmail.com>
On Thu, 2012-03-22 at 09:48 -0700, Khem Raj wrote:
> On Wed, Mar 21, 2012 at 9:22 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > On Wed, Mar 21, 2012 at 6:23 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> >>
> >> -DISTROOVERRIDES ?= "${DISTRO}"
> >> +DISTROOVERRIDES ?= "${@d.getVar('DISTRO', True) or ''}"
> >
> > whats wrong with patch I proposed ?
>
> Richard
>
> I was in same situation as Denys when I did that patch. I think
> this could be a good patch to consider
I agree and its merged! :)
Cheers,
Richard
next prev parent reply other threads:[~2012-03-22 18:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 3:33 [PATCH 0/4] stash gcc-cross buildtree and add recipe class override Khem Raj
2012-02-24 3:33 ` [PATCH 1/4] glib-networking: Add intltools-native to DEPENDS Khem Raj
2012-02-24 3:33 ` [PATCH 2/4] classes: Add recipe class to overrides Khem Raj
2012-02-24 16:20 ` Richard Purdie
2012-02-24 17:02 ` Khem Raj
2012-02-24 3:33 ` [PATCH 3/4] default-distrovars: Add empty weak definition for DISTRO variable Khem Raj
2012-02-24 16:21 ` Richard Purdie
2012-02-24 17:05 ` Khem Raj
2012-03-05 21:36 ` Saul Wold
2012-03-05 23:02 ` Khem Raj
2012-03-22 1:23 ` Denys Dmytriyenko
2012-03-22 4:22 ` Khem Raj
2012-03-22 16:48 ` Khem Raj
2012-03-22 17:52 ` Richard Purdie [this message]
2012-02-24 3:33 ` [PATCH 4/4] gcc: Stash the gcc-cross builddir to reuse in libgcc and gcc-runtime Khem Raj
2012-02-27 19:57 ` [PATCH 0/4] stash gcc-cross buildtree and add recipe class override Khem Raj
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=1332438722.9740.290.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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