From: Patrick Ohly <patrick.ohly@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] classes/buildstats: don't expand variable pointing to SystemStats
Date: Wed, 04 Jan 2017 14:05:03 +0100 [thread overview]
Message-ID: <1483535103.28169.52.camel@intel.com> (raw)
In-Reply-To: <af03426da1f2d00149a2021b8d681b2dcef3a1ea.1482376395.git.paul.eggleton@linux.intel.com>
On Thu, 2016-12-22 at 16:13 +1300, Paul Eggleton wrote:
> We're placing an object into the datastore - it's very definitely not
> something we want to be expanding.
Why does it matter? Is it faster to tell getVar() that expansion isn't
necessary?
I'm fine with the change, I'm just trying to understand whether this
merely cosmetic or has some real impact.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-01-04 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 3:13 [PATCH 0/3] Misc correctness fixes Paul Eggleton
2016-12-22 3:13 ` [PATCH 1/3] meta: use require instead of include when file should exist Paul Eggleton
2016-12-22 3:13 ` [PATCH 2/3] oe-selftest: fix behaviour if oe-selftest.log is a dangling symlink Paul Eggleton
2016-12-22 3:13 ` [PATCH 3/3] classes/buildstats: don't expand variable pointing to SystemStats Paul Eggleton
2017-01-04 13:05 ` Patrick Ohly [this message]
2017-01-09 1:50 ` 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=1483535103.28169.52.camel@intel.com \
--to=patrick.ohly@intel.com \
--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.