From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: a.mestdagh3@gmail.com, aaron.mestdagh@barco.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/fluent-bit: bump fluent-bit to 5.1.2
Date: Sat, 24 Oct 2026 23:10:09 +0200 [thread overview]
Message-ID: <at0en-vX3QeYjLvk@windsurf> (raw)
In-Reply-To: <20261024190338.329172-1-thomas@devoogdt.com>
On Sat, Oct 24, 2026 at 09:03:38PM +0200, Thomas Devoogdt wrote:
> From: Aaron Mestdagh <aaron.mestdagh@barco.com>
>
> Upgrade from 4.2.0 to 5.1.2, bringing multi-worker network ingestion
> and improved OpenTelemetry processing.
>
> The 5.x releases also add Google Cloud Storage output, Windows Event
> Tracing input, NVIDIA GPU metrics, and new metrics processors, alongside
> FIPS, TLS, and proxy improvements.
>
> Signed-off-by: Aaron Mestdagh <aaron.mestdagh@barco.com>
> Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>
I've updated the Upstream: tag to point to the commit merged upstream,
and applied. Thanks a lot!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-24 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 16:42 [Buildroot] [PATCH 4/4] package/fluent-bit: bump fluent-bit to 5.1.2 Aaron Mestdagh
2026-10-22 21:03 ` Thomas Petazzoni via buildroot
2026-10-22 21:12 ` Thomas Devoogdt
2026-10-24 19:03 ` [Buildroot] [PATCH v2] " Thomas Devoogdt
2026-10-24 21:10 ` 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=at0en-vX3QeYjLvk@windsurf \
--to=buildroot@buildroot.org \
--cc=a.mestdagh3@gmail.com \
--cc=aaron.mestdagh@barco.com \
--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 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.