From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Zabbix addon
Date: Thu, 30 Mar 2023 14:43:39 +0200 [thread overview]
Message-ID: <86293b77-176e-48d2-de66-01f156a202b0@ipfire.org> (raw)
In-Reply-To: <139ee284e4753449b0ee8b93da93dd77758d6973.camel@sicho.home>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Hi Robin,
On 30/03/2023 09:59, Robin Roevens wrote:
> Hi Adolf
>
> I know. I'm keeping watch on the upstream updates.
Good to know.
> "The problem" is that the agent code is released in one source tree with agent2, server, frontend, windows agent, etc.. and they all share the same version on each release but that doesn't necessary mean there are actual changes on the agent code itself. So I'm keeping track of the changelogs for any changes on the Linux agent itself, but since 6.0.6 there weren't any substantial changes, if any, on the code of the Linux agent.
> So I can provide those update patches, but it would actually just be cosmetic :-).
I agree that would not make sense to do.
I will leave it in your capable hands then to recognise when an update is required.
Regards,
Adolf.
>
> Regards
> Robin
>
>
> Adolf Belka schreef op di 28-03-2023 om 09:56 [+0200]:
>> Hi Robin,
>>
>> I have noticed that the zabbix_agentd addon is at 6.0.6 (LTS) but the LTS branch is now at 6.0.14
>>
>> Could you look at doing an update patch for it.
>>
>>
>> Regards,
>>
>> Adolf.
>>
>>
>
> --
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door *MailScanner* <http://www.mailscanner.info/> en lijkt schoon te zijn.
next parent reply other threads:[~2023-03-30 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <139ee284e4753449b0ee8b93da93dd77758d6973.camel@sicho.home>
2023-03-30 12:43 ` Adolf Belka [this message]
2023-03-28 7:56 Adolf Belka
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=86293b77-176e-48d2-de66-01f156a202b0@ipfire.org \
--to=adolf.belka@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