From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libxcrypt: Version bump. 4.4.36 -> 4.4.37
Date: Thu, 16 Jan 2025 17:09:36 +0100 [thread overview]
Message-ID: <20250116160936.427177-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250102183904.2201787-1-christian.melki@t2data.com>
Thanks, applied as 782bbd8d2dc96758006497c85a741cadd26b8755.
Michael
[sent from post-receive hook]
On Thu, 16 Jan 2025 17:09:36 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Minor changes.
> https://github.com/besser82/libxcrypt/releases/tag/v4.4.37
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250102183904.2201787-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libxcrypt.make b/rules/libxcrypt.make
> index e048968d0cc4..47198330ccd9 100644
> --- a/rules/libxcrypt.make
> +++ b/rules/libxcrypt.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBXCRYPT) += libxcrypt
> #
> # Paths and names
> #
> -LIBXCRYPT_VERSION := 4.4.36
> -LIBXCRYPT_MD5 := b84cd4104e08c975063ec6c4d0372446
> +LIBXCRYPT_VERSION := 4.4.37
> +LIBXCRYPT_MD5 := 13b528d04c74dab3c1c5471430161a8f
> LIBXCRYPT := libxcrypt-$(LIBXCRYPT_VERSION)
> LIBXCRYPT_SUFFIX := tar.xz
> LIBXCRYPT_URL := https://github.com/besser82/libxcrypt/releases/download/v$(LIBXCRYPT_VERSION)/$(LIBXCRYPT).$(LIBXCRYPT_SUFFIX)
prev parent reply other threads:[~2025-01-16 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 18:39 [ptxdist] [PATCH] " Christian Melki
2025-01-16 16:09 ` 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=20250116160936.427177-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