All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: Richard Purdie <richard.purdie@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: [RFC] file checksum cache refactoring
Date: Fri, 19 Feb 2016 16:34:36 +0200	[thread overview]
Message-ID: <1455892476.2298.11.camel@linux.intel.com> (raw)

Hi,

I pushed a patchset for inspection here:
http://git.openembedded.org/openembedded-core-contrib/log/?h=marquiz/bi
tbake/checksum-refactor

The first three patches are refactoring that could be merged without
breaking anything, the last patch extending the SignatureGenerator API.

The two last patches are something that could be merged at some later
point as they make the new API mandatory.

Any comments and suggestions are welcome.


Cheers,
  Markus

----------------------------------------------------------------
Markus Lehtonen (5):
      bb/siggen: drop commented-out code
      Move file checksum cache out of SignatureGenerator
      SignatureGenerator: add checksum_cache argument to get_taskhash()
      SignatureGenerator: make checksum_cache arg of get_taskhash()
mandatory
      bb/fetch2: drop checksum cache

 lib/bb/cooker.py          |  2 --
 lib/bb/fetch2/__init__.py | 18 ------------------
 lib/bb/runqueue.py        | 13 +++++++++++--
 lib/bb/siggen.py          | 29 +++--------------------------
 4 files changed, 14 insertions(+), 48 deletions(-)


             reply	other threads:[~2016-02-19 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 14:34 Markus Lehtonen [this message]
2016-02-19 14:36 ` [RFC] file checksum cache refactoring Markus Lehtonen

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=1455892476.2298.11.camel@linux.intel.com \
    --to=markus.lehtonen@linux.intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@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.