From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v5 0/6] zabbix_agentd: Update to v6.0.6 (LTS)
Date: Wed, 06 Jul 2022 10:11:01 +0000 [thread overview]
Message-ID: <05e252cf-1b59-95bf-67f7-cd86edc3f2c9@ipfire.org> (raw)
In-Reply-To: <BF6A22B0-42C7-4430-9CA5-F59A6F68DD2B@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
Hello Robin,
> Hello Robin,
>
> I trust you that everything has been addressed.
>
> I think this is ready to be merged.
I just did so, and that series now landed in "next": https://git.ipfire.org/?p=ipfire-2.x.git;a=search;h=refs/heads/next;s=Robin+Roevens;st=author
You will see the changes being released with Core Update 170.
Apologies for the tardy process on our end, and thanks for being both patient and
persistent. In the future, please continue to prod and poke at us to keep things
moving. :-)
All the best,
Peter Müller
>
> 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 prev parent reply other threads:[~2022-07-06 10:11 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
2022-07-06 10:11 ` Peter Müller [this message]
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=05e252cf-1b59-95bf-67f7-cd86edc3f2c9@ipfire.org \
--to=peter.mueller@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