From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Further optimizations to the sstate.bbclass
Date: Fri, 11 May 2012 12:17:53 -0500 [thread overview]
Message-ID: <cover.1336756602.git.mark.hatle@windriver.com> (raw)
A few minor changes to the generation of the fixmepaths file in
the sstate cache file generation can lead to significant performance
improvements in recipes that generate large file sets.
The following changes since commit 9cd30beba77497288eeb2545920bc23f2a77cf16:
.gitignore: add /bitbake to the ignore list for external distributions (2012-05-11 17:59:53 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib mhatle/sstate
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/sstate
Mark Hatle (1):
sstate.bbclass: Optimize the generation and install path fixups
meta/classes/sstate.bbclass | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
--
1.7.3.4
next reply other threads:[~2012-05-11 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 17:17 Mark Hatle [this message]
2012-05-11 17:17 ` [PATCH 1/1] sstate.bbclass: Optimize the generation and install path fixups Mark Hatle
2012-05-16 18:04 ` [PATCH 0/1] Further optimizations to the sstate.bbclass Saul Wold
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=cover.1336756602.git.mark.hatle@windriver.com \
--to=mark.hatle@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