From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: zhengruoqin <zhengrq.fnst@cn.fujitsu.com>
Cc: meta-virtualization@yoctoproject.org
Subject: Re: [meta-virtualization] [PATCH] python3-dogpile.cache: upgrade 1.0.2 -> 1.1.1
Date: Thu, 10 Dec 2020 15:59:22 -0500 [thread overview]
Message-ID: <20201210205921.GB4078@gmail.com> (raw)
In-Reply-To: <1607403570-56215-1-git-send-email-zhengrq.fnst@cn.fujitsu.com> <1607403611-56302-1-git-send-email-zhengrq.fnst@cn.fujitsu.com> <1607403624-56341-1-git-send-email-zhengrq.fnst@cn.fujitsu.com> <1607403680-56464-1-git-send-email-zhengrq.fnst@cn.fujitsu.com> <1607403671-56404-1-git-send-email-zhengrq.fnst@cn.fujitsu.com> <1607403688-56502-1-git-send-email-zhengrq.fnst@cn.fujitsu.com>
merged.
Bruce
In message: [meta-virtualization] [PATCH] python3-dogpile.cache: upgrade 1.0.2 -> 1.1.1
on 08/12/2020 zhengruoqin wrote:
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
> ---
> ...-dogpile.cache_1.0.2.bb => python3-dogpile.cache_1.1.1.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta-openstack/recipes-devtools/python/{python3-dogpile.cache_1.0.2.bb => python3-dogpile.cache_1.1.1.bb} (73%)
>
> diff --git a/meta-openstack/recipes-devtools/python/python3-dogpile.cache_1.0.2.bb b/meta-openstack/recipes-devtools/python/python3-dogpile.cache_1.1.1.bb
> similarity index 73%
> rename from meta-openstack/recipes-devtools/python/python3-dogpile.cache_1.0.2.bb
> rename to meta-openstack/recipes-devtools/python/python3-dogpile.cache_1.1.1.bb
> index 21b596fc..627d7db0 100644
> --- a/meta-openstack/recipes-devtools/python/python3-dogpile.cache_1.0.2.bb
> +++ b/meta-openstack/recipes-devtools/python/python3-dogpile.cache_1.1.1.bb
> @@ -4,8 +4,8 @@ SECTION = "devel/python"
> LICENSE = "BSD"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=46e560ef3e93a33b284504845ea6a11d"
>
> -SRC_URI[md5sum] = "a325ec142d690269573a872e24fc1cb6"
> -SRC_URI[sha256sum] = "64fda39d25b46486a4876417ca03a4af06f35bfadba9f59613f9b3d748aa21ef"
> +SRC_URI[md5sum] = "3cf83a593a1a1bc17b89d14917f66ef0"
> +SRC_URI[sha256sum] = "40147b19696f387415a7efaaa4cf8ea0b5d31bdd1b53e5187e75d48ddfee9f0e"
>
> inherit setuptools3 pypi
>
> --
> 2.25.1
>
>
>
>
>
>
prev parent reply other threads:[~2020-12-10 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 4:59 [meta-virtualization] [PATCH] python3-barbicanclient: upgrade 5.0.0 -> 5.0.1 zhengruoqin
2020-12-08 5:00 ` [meta-virtualization] [PATCH] python3-castellan: upgrade 3.6.0 -> 3.7.0 zhengruoqin
2020-12-08 5:00 ` [meta-virtualization] [PATCH] python3-cliff: upgrade 3.4.0 -> 3.5.0 zhengruoqin
2020-12-08 5:01 ` [meta-virtualization] [PATCH] python3-django-nose: upgrade 1.4 -> 1.4.7 zhengruoqin
2020-12-08 5:01 ` [meta-virtualization] [PATCH] python3-designateclient: upgrade 4.0.0 -> 4.1.0 zhengruoqin
2020-12-08 5:01 ` [meta-virtualization] [PATCH] python3-dogpile.cache: upgrade 1.0.2 -> 1.1.1 zhengruoqin
2020-12-10 20:59 ` Bruce Ashfield [this message]
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=20201210205921.GB4078@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@yoctoproject.org \
--cc=zhengrq.fnst@cn.fujitsu.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.