From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 1/4] package/fluent-bit: bump to version 2.1.7
Date: Sun, 23 Jul 2023 12:01:21 +0200 [thread overview]
Message-ID: <20230723120121.569135b2@windsurf> (raw)
In-Reply-To: <20230723092314.129079-1-thomas@devoogdt.com>
Hello Thomas,
On Sun, 23 Jul 2023 11:23:11 +0200
Thomas Devoogdt <thomas@devoogdt.com> wrote:
> Fluent Bit v2.1 is the start of the new stable series of the project.
>
> Release Notes:
>
> https://fluentbit.io/announcements/v2.1.0/
> https://fluentbit.io/announcements/v2.1.1/
> https://fluentbit.io/announcements/v2.1.2/
> https://fluentbit.io/announcements/v2.1.3/
> https://fluentbit.io/announcements/v2.1.4/
> https://fluentbit.io/announcements/v2.1.5/
> https://fluentbit.io/announcements/v2.1.6/
> https://fluentbit.io/announcements/v2.1.7/
>
> Fluent Bit v2.1.7 contains this list of upstreamed patches:
>
> https://github.com/fluent/fluent-bit/pull/7266
> https://github.com/fluent/fluent-bit/pull/7254
> https://github.com/fluent/fluent-bit/pull/7253
>
> So the old patches can be dropped.
>
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
> ---
> v2: bump from 2.1.3 to 2.1.4
> v3: bump from 2.1.4 to 2.1.7
> ---
> .checkpackageignore | 3 -
> .../0001-lib-cfl-fixup-static_assert.patch | 33 -----
> .../0002-lib-c-ares-fixup-static_assert.patch | 56 --------
> .../fluent-bit/0003-fix-build-without-C.patch | 131 ------------------
> package/fluent-bit/fluent-bit.hash | 2 +-
> package/fluent-bit/fluent-bit.mk | 2 +-
> 6 files changed, 2 insertions(+), 225 deletions(-)
> delete mode 100644 package/fluent-bit/0001-lib-cfl-fixup-static_assert.patch
> delete mode 100644 package/fluent-bit/0002-lib-c-ares-fixup-static_assert.patch
> delete mode 100644 package/fluent-bit/0003-fix-build-without-C.patch
Patches 1/4 to 3/4 applied, thanks! On patch 4/4, I have some
questions, so I will reply to it separately.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-23 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 13:32 [Buildroot] [PATCH v2 1/4] package/fluent-bit: bump to version 2.1.4 Thomas Devoogdt
2023-06-10 13:32 ` [Buildroot] [PATCH v2 2/4] package/fluent-bit: use the system provided LuaJIT Thomas Devoogdt
2023-06-10 13:32 ` [Buildroot] [PATCH v2 3/4] package/fluent-bit: drop cxx handling Thomas Devoogdt
2023-06-10 13:32 ` [Buildroot] [PATCH v2 4/4] package/fluent-bit: rework wasm handling Thomas Devoogdt
2023-07-23 9:23 ` [Buildroot] [PATCH v3 1/4] package/fluent-bit: bump to version 2.1.7 Thomas Devoogdt
2023-07-23 9:23 ` [Buildroot] [PATCH v3 2/4] package/fluent-bit: use the system provided LuaJIT Thomas Devoogdt
2023-07-23 9:23 ` [Buildroot] [PATCH v3 3/4] package/fluent-bit: drop cxx handling Thomas Devoogdt
2023-07-23 9:23 ` [Buildroot] [PATCH v3 4/4] package/fluent-bit: rework wasm handling Thomas Devoogdt
2023-07-23 10:06 ` Thomas Petazzoni via buildroot
2023-07-24 8:29 ` Thomas Devoogdt
2023-07-24 8:45 ` Thomas Petazzoni via buildroot
2023-07-24 12:04 ` [Buildroot] [PATCH v4] " Thomas Devoogdt
2023-07-25 16:38 ` Thomas Petazzoni via buildroot
2023-07-23 10:01 ` Thomas Petazzoni via buildroot [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=20230723120121.569135b2@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas@devoogdt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox