From: "Diego Santa Cruz" <diego.santacruz@spinetix.com>
To: akuster808 <akuster808@gmail.com>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [gatesgarth][meta-multimedia][PATCH 1/2] gssdp: Upgrade to 1.2.2 -> 1.2.3
Date: Mon, 11 Jan 2021 14:52:08 +0000 [thread overview]
Message-ID: <DB6PR0102MB26301088AE72EDF1F07AEF5088AB0@DB6PR0102MB2630.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <7ef6b205-3759-737c-6c16-677556062757@gmail.com>
> -----Original Message-----
> From: akuster808 <akuster808@gmail.com>
> Sent: 11 January 2021 15:47
> To: Diego Santa Cruz <Diego.SantaCruz@spinetix.com>; openembedded-
> devel@lists.openembedded.org
> Subject: Re: [oe] [gatesgarth][meta-multimedia][PATCH 1/2] gssdp: Upgrade
> to 1.2.2 -> 1.2.3
>
>
>
> On 1/7/21 10:37 AM, Diego Santa Cruz via lists.openembedded.org wrote:
> > Dependency of gupnp 1.2.3
>
> Whats in the update?
>
From what I understand from https://gitlab.gnome.org/GNOME/gssdp/-/blob/gssdp-1.2.3/NEWS
* Bugfixes
* One API addition to support the fix / mitigation for CVE-2020-12695 in gupnp
--
Diego Santa Cruz, PhD
Technology Architect
spinetix.com
next prev parent reply other threads:[~2021-01-11 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 18:37 [gatesgarth][meta-multimedia][PATCH 1/2] gssdp: Upgrade to 1.2.2 -> 1.2.3 Diego Santa Cruz
2021-01-07 18:37 ` [gatesgarth][meta-multimedia][PATCH 2/2] gupnp: Upgrade to 1.2.2 -> 1.2.4 Diego Santa Cruz
2021-01-11 14:47 ` [oe] " akuster
2021-01-11 14:56 ` Diego Santa Cruz
2021-01-11 14:46 ` [oe] [gatesgarth][meta-multimedia][PATCH 1/2] gssdp: Upgrade to 1.2.2 -> 1.2.3 akuster
2021-01-11 14:52 ` Diego Santa Cruz [this message]
2021-01-11 17:48 ` Khem Raj
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=DB6PR0102MB26301088AE72EDF1F07AEF5088AB0@DB6PR0102MB2630.eurprd01.prod.exchangelabs.com \
--to=diego.santacruz@spinetix.com \
--cc=akuster808@gmail.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.