All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liping Ke <liping.ke@intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/4] Put extra requested fields into different cache files
Date: Mon, 09 May 2011 14:36:29 +0800	[thread overview]
Message-ID: <cover.1304922517.git.liping.ke@intel.com> (raw)

From: Liping Ke <liping.ke@intel.com>

Below four patches are for putting extra requested fields inito different
cache files instead of using only on bb_cache.dat. Now image creator need
extra three fields. And in the future, there might be more similar requests.
For each extra requestor, we will save the requested fields data into a
separate cache files so that those who don't need it will not be impacted
with larger fields and large data files.

Pull URL: git://git.pokylinux.org/poky-contrib.git
  Branch: lke/cache_impl
  Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=lke/cache_impl

Thanks,
    Liping Ke <liping.ke@intel.com>
---


Liping Ke (4):
  Introduce new param bitbake_mode into Cache.py
  Split Cache Data Retrieve method from Data Fields
  Introduce Extra required fields for image creator
  Implement independent cache for Extra Cache Fields Request

 bitbake/lib/bb/cache.py  |  189 +++++++++++++++++++++++++++++++++++++---------
 bitbake/lib/bb/cooker.py |   55 ++++++++++----
 2 files changed, 193 insertions(+), 51 deletions(-)



             reply	other threads:[~2011-05-09  6:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09  6:36 Liping Ke [this message]
2011-05-09  6:36 ` [PATCH 1/4] Put extra requested fields into different cache files Liping Ke
2011-05-09  6:36 ` [PATCH 2/4] " Liping Ke
2011-05-09  6:36 ` [PATCH 3/4] " Liping Ke
2011-05-09  6:36 ` [PATCH 4/4] " Liping Ke
2011-05-09  6:52 ` [PATCH 0/4][Image Creator]Put " Ke, Liping
2011-05-09  6:58   ` Ke, Liping
2011-05-09 11:52 ` Richard Purdie
2011-05-10  1:26   ` Ke, Liping
2011-05-11 16:07     ` Richard Purdie
2011-05-12  1:56       ` Ke, Liping

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.1304922517.git.liping.ke@intel.com \
    --to=liping.ke@intel.com \
    --cc=poky@yoctoproject.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 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.