From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: collectd conversion fixes
Date: Thu, 30 Jan 2025 13:15:53 +0100 [thread overview]
Message-ID: <7c00b46d-47cf-4b79-9b94-6ece4aeab321@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
Hi Arne,
Thanks and well done on figuring out the various changes that were missed in my original patch submission.
Some like the temperature related ones I can understand as my testing of my changes was done on my virtual testbed systems and they have no temperature sensors so nothing is generated on the system and hence nothing to migrate.
This is why I thought it would be good to get others input on what I had created in case I had missed anything.
Thanks again ,
Adolf.
reply other threads:[~2025-01-30 12:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7c00b46d-47cf-4b79-9b94-6ece4aeab321@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