From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: <yann.morin@orange.com>
Cc: <buildroot@buildroot.org>, Vincent Fazio <vfazio@gmail.com>,
Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH 0/2] package/filebeat: new package
Date: Sat, 26 Oct 2024 18:44:14 +0200 [thread overview]
Message-ID: <20241026184414.5924bc56@windsurf> (raw)
In-Reply-To: <cover.1699547993.git.yann.morin@orange.com>
Hello,
+Cc Christian Steward.
On Thu, 9 Nov 2023 17:39:54 +0100
<yann.morin@orange.com> wrote:
> This two-patch series introduces filebeat, an ElasticSearch-related tool
> to grab local log files and send them to a remote ElasticSearch server.
>
> It is a bit convoluted (see commit log), and requires a little extension
> in our golang-package infrastructure, which we introduce as the first
> patch in the series.
Christian, could you review this patch series, and especially PATCH
1/2, which touches the golang-package infrastructure?
Thanks a lot!
Thomas
--
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
next prev parent reply other threads:[~2024-10-26 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 16:39 [Buildroot] [PATCH 0/2] package/filebeat: new package yann.morin
2023-11-09 16:39 ` [Buildroot] [PATCH 1/2] package/pkg-golang: allow packages to provide extldflags yann.morin
2025-02-04 14:33 ` Fiona Klute via buildroot
2023-11-09 16:39 ` [Buildroot] [PATCH 2/2] package/filebeat: new package yann.morin
2024-10-26 16:44 ` Thomas Petazzoni via buildroot [this message]
2024-10-26 17:37 ` [Buildroot] [PATCH 0/2] " Christian Stewart via buildroot
-- strict thread matches above, loose matches on Subject: below --
2023-10-30 9:22 yann.morin
2024-11-18 6:35 ` yann.morin
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=20241026184414.5924bc56@windsurf \
--to=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@gmail.com \
--cc=yann.morin@orange.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