From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] wayland-protocols: Version bump. 1.28 -> 1.30.
Date: Tue, 22 Nov 2022 14:20:24 +0100 [thread overview]
Message-ID: <20221122132024.3160059-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221121195821.1941577-1-christian.melki@t2data.com>
Thanks, applied as a23c66da19691d293ddbeb84b44cc7bdb27d7544.
Michael
[sent from post-receive hook]
On Tue, 22 Nov 2022 14:20:24 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Not much happening between releases.
> The notable addition is a tearing control protocol.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20221121195821.1941577-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/wayland-protocols.make b/rules/wayland-protocols.make
> index 2e166bc2c9bb..bef3f9495d92 100644
> --- a/rules/wayland-protocols.make
> +++ b/rules/wayland-protocols.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_WAYLAND_PROTOCOLS) += wayland-protocols
> #
> # Paths and names
> #
> -WAYLAND_PROTOCOLS_VERSION := 1.28
> -WAYLAND_PROTOCOLS_MD5 := 391ac1ac30e96d2f5559e2cc40a4d924
> +WAYLAND_PROTOCOLS_VERSION := 1.30
> +WAYLAND_PROTOCOLS_MD5 := 000b0113e7fe73eb2da6dbaf54f8eca3
> WAYLAND_PROTOCOLS := wayland-protocols-$(WAYLAND_PROTOCOLS_VERSION)
> WAYLAND_PROTOCOLS_SUFFIX := tar.xz
> WAYLAND_PROTOCOLS_URL := https://gitlab.freedesktop.org/wayland/wayland-protocols/-/releases/$(WAYLAND_PROTOCOLS_VERSION)/downloads/$(WAYLAND_PROTOCOLS).$(WAYLAND_PROTOCOLS_SUFFIX)
prev parent reply other threads:[~2022-11-22 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 19:58 [ptxdist] [PATCH] " Christian Melki
2022-11-22 13:20 ` Michael Olbrich [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=20221122132024.3160059-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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