All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-networking] [PATCH] spice-protocol: upgrade 0.14.3 -> 0.14.4
Date: Wed, 23 Feb 2022 15:51:08 +0800	[thread overview]
Message-ID: <1645602670-28373-1-git-send-email-wangmy@fujitsu.com> (raw)

Major changes in 0.14.4
=======================
* Fix enum deprecation warning for visual studio
* Fix documentation typos in stream-device.h

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 .../{spice-protocol_1.14.3.bb => spice-protocol_0.14.4.bb}      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-networking/recipes-support/spice/{spice-protocol_1.14.3.bb => spice-protocol_0.14.4.bb} (89%)

diff --git a/meta-networking/recipes-support/spice/spice-protocol_1.14.3.bb b/meta-networking/recipes-support/spice/spice-protocol_0.14.4.bb
similarity index 89%
rename from meta-networking/recipes-support/spice/spice-protocol_1.14.3.bb
rename to meta-networking/recipes-support/spice/spice-protocol_0.14.4.bb
index 1ea606bb6d..9ce019ed86 100644
--- a/meta-networking/recipes-support/spice/spice-protocol_1.14.3.bb
+++ b/meta-networking/recipes-support/spice/spice-protocol_0.14.4.bb
@@ -8,7 +8,7 @@ HOMEPAGE = "https://spice-space.org"
 LICENSE = "BSD-3-Clause"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b37311cb5604f3e5cc2fb0fd23527e95"
 
-SRCREV = "90b57dace404db564a8e034ad4427b9951071bcd"
+SRCREV = "6f453a775d87087c6ba59fc180c1a1e466631a47"
 
 SRC_URI = "git://gitlab.freedesktop.org/spice/spice-protocol.git;protocol=https;branch=master"
 
-- 
2.25.1



             reply	other threads:[~2022-02-23  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  7:51 Wang Mingyu [this message]
2022-02-23  7:51 ` [oe] [meta-networking] [PATCH] tcpreplay: upgrade 4.4.0 -> 4.4.1 Wang Mingyu
2022-02-23  7:51 ` [oe] [meta-networking] [PATCH] wolfssl: upgrade 5.1.0- > 5.2.0 Wang Mingyu

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=1645602670-28373-1-git-send-email-wangmy@fujitsu.com \
    --to=wangmy@fujitsu.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.