From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/lz4: bump to version 1.9.4
Date: Tue, 08 Nov 2022 20:55:51 +0100 [thread overview]
Message-ID: <875yfpi5ko.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221023091009.18544-2-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sun, 23 Oct 2022 11:10:09 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> LZ4 v1.9.4 is a maintenance release, featuring a substantial amount
> (~350 commits) of minor fixes and improvements, making it a recommended
> upgrade. The stable portion of liblz4 API is unmodified, making this
> release a drop-in replacement for existing features.
> - Drop patch (already in version)
> - Update hash of lib/LICENSE (update in year with
> https://github.com/lz4/lz4/commit/87a80acbe7872b9da7d56f7005ffd1b715e87c93)
> https://github.com/lz4/lz4/releases/tag/v1.9.4
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.08.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-08 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 9:10 [Buildroot] [PATCH 1/2] package/lz4: fix LZ4_CPE_ID_VENDOR Fabrice Fontaine
2022-10-23 9:10 ` [Buildroot] [PATCH 2/2] package/lz4: bump to version 1.9.4 Fabrice Fontaine
2022-11-08 19:55 ` Peter Korsgaard [this message]
2022-10-28 6:54 ` [Buildroot] [PATCH 1/2] package/lz4: fix LZ4_CPE_ID_VENDOR Thomas Petazzoni via buildroot
2022-11-08 19:55 ` Peter Korsgaard
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=875yfpi5ko.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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.