From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v5 0/6] zabbix_agentd: Update to v6.0.6 (LTS)
Date: Fri, 01 Jul 2022 18:05:14 +0100 [thread overview]
Message-ID: <BF6A22B0-42C7-4430-9CA5-F59A6F68DD2B@ipfire.org> (raw)
In-Reply-To: <20220630101555.13438-1-robin.roevens@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hello Robin,
I trust you that everything has been addressed.
I think this is ready to be merged.
Great work!
-Michael
> On 30 Jun 2022, at 11:15, Robin Roevens <robin.roevens(a)disroot.org> wrote:
>
> Hi all
>
> A renewal of this patchset, now for zabbix_agentd 6.0.6, the latest LTS
> version at the moment.
>
> Except for the version nothing has changed in this set since my previous
> submission. So please see
> https://lists.ipfire.org/pipermail/development/2022-March/012624.html
> for the summary of this patch set.
>
> Hopefully this can be included in Core 170?..
>
> Regards
>
> Robin Roevens
>
>
>
> --
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>
next parent reply other threads:[~2022-07-01 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220630101555.13438-1-robin.roevens@disroot.org>
2022-07-01 17:05 ` Michael Tremer [this message]
2022-07-06 10:11 ` Peter Müller
2022-07-06 10:20 ` Michael Tremer
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=BF6A22B0-42C7-4430-9CA5-F59A6F68DD2B@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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