From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2] python-smartpm: use md5 as the digest for rpm_sys channel
Date: Wed, 14 Sep 2016 11:46:05 +0300 [thread overview]
Message-ID: <1473842766-27585-1-git-send-email-markus.lehtonen@linux.intel.com> (raw)
When reading smartpm sources more closely I found out that it has an internal
utility function for doing file hashes. It does hashing in a more memory
efficient way, processing the file in chunks. Thus, it is better to use it
instead of blindly reading the whole file into memory as v1 of this patch did.
Markus Lehtonen (1):
python-smartpm: use md5 as the digest for rpm_sys channel
...m_sys-use-md5sum-instead-of-mtime-as-the-.patch | 38 ++++++++++++++++++++++
meta/recipes-devtools/python/python-smartpm_git.bb | 1 +
2 files changed, 39 insertions(+)
create mode 100644 meta/recipes-devtools/python/python-smartpm/channels-rpm_sys-use-md5sum-instead-of-mtime-as-the-.patch
--
2.6.6
next reply other threads:[~2016-09-14 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 8:46 Markus Lehtonen [this message]
2016-09-14 8:46 ` [PATCH v2] python-smartpm: use md5 as the digest for rpm_sys channel 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=1473842766-27585-1-git-send-email-markus.lehtonen@linux.intel.com \
--to=markus.lehtonen@linux.intel.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