From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] sdl2-image: Version bump. 2.6.2 -> 2.6.3.
Date: Fri, 10 Feb 2023 15:17:22 +0100 [thread overview]
Message-ID: <20230210141722.3534207-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230207091002.2418139-2-christian.melki@t2data.com>
Thanks, applied as b6293107db5b0ab2ad6a9d9d884062adfb5b396c.
Michael
[sent from post-receive hook]
On Fri, 10 Feb 2023 15:17:22 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Very minor bugfix release.
> https://github.com/libsdl-org/SDL_image/releases/tag/release-2.6.3
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230207091002.2418139-2-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/sdl2-image.make b/rules/sdl2-image.make
> index a01f69daff61..bdd3c7415c31 100644
> --- a/rules/sdl2-image.make
> +++ b/rules/sdl2-image.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_SDL2_IMAGE) += sdl2-image
> #
> # Paths and names
> #
> -SDL2_IMAGE_VERSION := 2.6.2
> -SDL2_IMAGE_MD5 := 35da7c375b1c187b0f684c1c83b3b9c3
> +SDL2_IMAGE_VERSION := 2.6.3
> +SDL2_IMAGE_MD5 := 191c3eb49cc2dce30abff81398a92e81
> SDL2_IMAGE := SDL2_image-$(SDL2_IMAGE_VERSION)
> SDL2_IMAGE_SUFFIX := tar.gz
> SDL2_IMAGE_URL := https://www.libsdl.org/projects/SDL_image/release/$(SDL2_IMAGE).$(SDL2_IMAGE_SUFFIX)
next prev parent reply other threads:[~2023-02-10 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 9:10 [ptxdist] [PATCH] sdl2: Version bump. 2.26.2 -> 2.26.3 Christian Melki
2023-02-07 9:10 ` [ptxdist] [PATCH] sdl2-image: Version bump. 2.6.2 -> 2.6.3 Christian Melki
2023-02-10 14:17 ` Michael Olbrich [this message]
2023-02-10 14:17 ` [ptxdist] [APPLIED] sdl2: Version bump. 2.26.2 -> 2.26.3 Michael Olbrich
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=20230210141722.3534207-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