From: Richard Purdie <rpurdie@rpsys.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] More quoting fixes
Date: Wed, 29 Feb 2012 13:26:01 +0000 [thread overview]
Message-ID: <1330521961.24508.43.camel@ted> (raw)
In-Reply-To: <CAP9ODKpPUtNpV0Wc91kvehnf=1OpYtKdJ411-+kV8Z=GADOKiQ@mail.gmail.com>
On Wed, 2012-02-29 at 10:19 -0300, Otavio Salvador wrote:
> On Wed, Feb 29, 2012 at 09:59, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > -export VERBOSE=1
> > +export VERBOSE="1"
>
> I fully agree with the change but here it doesn't raise a parser
> error. Isn't it expected to happen?
No. I added something to bitbake a short while ago and these are parser
errors now!
Cheers,
Richard
next prev parent reply other threads:[~2012-02-29 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 12:59 [PATCH 0/1] More quoting fixes Paul Eggleton
2012-02-29 12:59 ` [PATCH 1/1] " Paul Eggleton
2012-02-29 13:19 ` Otavio Salvador
2012-02-29 13:24 ` Paul Eggleton
2012-02-29 13:26 ` Richard Purdie [this message]
2012-02-29 13:27 ` Otavio Salvador
2012-02-29 13:14 ` [PATCH 0/1] " 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=1330521961.24508.43.camel@ted \
--to=rpurdie@rpsys.net \
--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