All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Trevor Gamblin" <trevor.gamblin@windriver.com>
To: Leon Anavi <leon.anavi@konsulko.com>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-python][PATCH 03/10] python3-pyperf: Upgrade 2.0.0 -> 2.1.0
Date: Wed, 20 Jan 2021 08:34:35 -0500	[thread overview]
Message-ID: <341a7fa2-a838-e067-5495-d2e3793942fe@windriver.com> (raw)
In-Reply-To: <20210119173746.24694-3-leon.anavi@konsulko.com>

[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]


On 2021-01-19 12:37 p.m., Leon Anavi wrote:
> - The compare_to command now computes the geometric mean.
> - The compare_to command no longer displays percentages: display
>    less numbers to make the output easier to read. Also, percentage
>    were almost the same values than the xxx faster or xxx slower
>    values, but rounded differenly which introduced confusion.
> - Project moved to https://github.com/psf/pyperf/
> - system command now only emits a warning rather than failing with
>    a hard error if it fails to get or set the frequency of a CPU.
> - The pyperf project is now covered by the PSF Code of Conduct.
>
> Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Acked-by: Trevor Gamblin <trevor.gamblin@windriver.com>
> ---
>   .../{python3-pyperf_2.0.0.bb => python3-pyperf_2.1.0.bb}       | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
>   rename meta-python/recipes-devtools/python/{python3-pyperf_2.0.0.bb => python3-pyperf_2.1.0.bb} (84%)
>
> diff --git a/meta-python/recipes-devtools/python/python3-pyperf_2.0.0.bb b/meta-python/recipes-devtools/python/python3-pyperf_2.1.0.bb
> similarity index 84%
> rename from meta-python/recipes-devtools/python/python3-pyperf_2.0.0.bb
> rename to meta-python/recipes-devtools/python/python3-pyperf_2.1.0.bb
> index 7ced7d017..b57ea16eb 100644
> --- a/meta-python/recipes-devtools/python/python3-pyperf_2.0.0.bb
> +++ b/meta-python/recipes-devtools/python/python3-pyperf_2.1.0.bb
> @@ -13,8 +13,7 @@ Features: \
>   LICENSE = "MIT"
>   LIC_FILES_CHKSUM = "file://COPYING;md5=78bc2e6e87c8c61272937b879e6dc2f8"
>   
> -SRC_URI[md5sum] = "7f62d3f6fc5475138791d3d883fdf4cd"
> -SRC_URI[sha256sum] = "2189fbc4af08d519f85468e70e32c902eab0f1341b2c41028b94b2832d3169a7"
> +SRC_URI[sha256sum] = "1257d673d89fdcdbaec8077afeb365e7a94739c1b263572b09403cac25708ad3"
>   
>   DEPENDS += "${PYTHON_PN}-six-native"
>   
>
> 
>

[-- Attachment #2: Type: text/html, Size: 2886 bytes --]

  reply	other threads:[~2021-01-20 13:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 17:37 [meta-python][PATCH 01/10] python3-colorlog: Upgrade 4.6.2 -> 4.7.2 Leon Anavi
2021-01-19 17:37 ` [meta-python][PATCH 02/10] python3-pyephem: Upgrade 3.7.7.0 -> 3.7.7.1 Leon Anavi
2021-01-20 13:34   ` [oe] " Trevor Gamblin
2021-01-19 17:37 ` [meta-python][PATCH 03/10] python3-pyperf: Upgrade 2.0.0 -> 2.1.0 Leon Anavi
2021-01-20 13:34   ` Trevor Gamblin [this message]
2021-01-19 17:37 ` [meta-python][PATCH 04/10] python3-cheetah: Upgrade 3.2.5 -> 3.2.6 Leon Anavi
2021-01-20 13:34   ` [oe] " Trevor Gamblin
2021-01-19 17:37 ` [meta-python][PATCH 05/10] python3-pyscaffold: Upgrade 3.3 -> 3.3.1 Leon Anavi
2021-01-20 13:35   ` [oe] " Trevor Gamblin
2021-01-19 17:37 ` [meta-python][PATCH 06/10] python3-lxml: Upgrade 4.6.1 -> 4.6.2 Leon Anavi
2021-01-20 13:35   ` [oe] " Trevor Gamblin
2021-01-19 17:37 ` [meta-python][PATCH 07/10] python3-openpyxl: Upgrade 3.0.5 -> 3.0.6 Leon Anavi
2021-01-20 13:36   ` [oe] " Trevor Gamblin
2021-01-19 17:37 ` [meta-python][PATCH 08/10] python3-pymysql: Upgrade 0.10.1 -> 1.0.2 Leon Anavi
2021-01-20 13:36   ` [oe] " Trevor Gamblin
2021-01-19 17:37 ` [meta-python][PATCH 09/10] python3-dbus-next: Upgrade 0.1.4 -> 0.2.2 Leon Anavi
2021-01-20 13:36   ` [oe] " Trevor Gamblin
2021-01-19 17:37 ` [meta-python][PATCH 10/10] python3-yappi: Upgrade 1.3.0 -> 1.3.2 Leon Anavi
2021-01-20 13:36   ` [oe] " Trevor Gamblin
2021-01-20 13:34 ` [oe] [meta-python][PATCH 01/10] python3-colorlog: Upgrade 4.6.2 -> 4.7.2 Trevor Gamblin

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=341a7fa2-a838-e067-5495-d2e3793942fe@windriver.com \
    --to=trevor.gamblin@windriver.com \
    --cc=leon.anavi@konsulko.com \
    --cc=openembedded-devel@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 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.