From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Matthias Heiserer <m.heiserer@proxmox.com>,
pve-devel@lists.proxmox.com
Subject: [pve-devel] applied: [pbs-devel] [PATCH proxmox-backup] fix #4165: SMART: add raw field
Date: Fri, 23 Sep 2022 12:28:29 +0200 [thread overview]
Message-ID: <0cec4592-8711-a9fd-09a7-6ab0028b58fc@proxmox.com> (raw)
In-Reply-To: <20220721104559.302270-1-m.heiserer@proxmox.com>
Am 21/07/2022 um 12:45 schrieb Matthias Heiserer:
> This makes it consistent with the naming scheme in PVE/GUI.
> Keep value for API stability reasons, and remove it in next major version.
>
> Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
> ---
> src/tools/disks/smart.rs | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
>
applied, with Dominik's T-b/R-b and a small follow up (see below), thanks!
> diff --git a/src/tools/disks/smart.rs b/src/tools/disks/smart.rs
> index 3738cdfd..787971e9 100644
> --- a/src/tools/disks/smart.rs
> +++ b/src/tools/disks/smart.rs
> @@ -25,8 +25,11 @@ pub enum SmartStatus {
> pub struct SmartAttribute {
> /// Attribute name
> name: String,
> - /// Attribute raw value
> + // fixme remove value in major release
Please capitalize FIXME, as that way most editors will highlight it by default,
additionally include the specific major release this should be removed. I changed
it to:
// FIXME: remove value with next major relase (PBS 3.0)
WARNING: multiple messages have this Message-ID
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Matthias Heiserer <m.heiserer@proxmox.com>,
pve-devel@lists.proxmox.com
Subject: [pbs-devel] applied: [PATCH proxmox-backup] fix #4165: SMART: add raw field
Date: Fri, 23 Sep 2022 12:28:29 +0200 [thread overview]
Message-ID: <0cec4592-8711-a9fd-09a7-6ab0028b58fc@proxmox.com> (raw)
In-Reply-To: <20220721104559.302270-1-m.heiserer@proxmox.com>
Am 21/07/2022 um 12:45 schrieb Matthias Heiserer:
> This makes it consistent with the naming scheme in PVE/GUI.
> Keep value for API stability reasons, and remove it in next major version.
>
> Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
> ---
> src/tools/disks/smart.rs | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
>
applied, with Dominik's T-b/R-b and a small follow up (see below), thanks!
> diff --git a/src/tools/disks/smart.rs b/src/tools/disks/smart.rs
> index 3738cdfd..787971e9 100644
> --- a/src/tools/disks/smart.rs
> +++ b/src/tools/disks/smart.rs
> @@ -25,8 +25,11 @@ pub enum SmartStatus {
> pub struct SmartAttribute {
> /// Attribute name
> name: String,
> - /// Attribute raw value
> + // fixme remove value in major release
Please capitalize FIXME, as that way most editors will highlight it by default,
additionally include the specific major release this should be removed. I changed
it to:
// FIXME: remove value with next major relase (PBS 3.0)
next prev parent reply other threads:[~2022-09-23 10:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 10:45 [pve-devel] " Matthias Heiserer
2022-07-21 10:45 ` [pbs-devel] " Matthias Heiserer
2022-07-21 10:45 ` [pve-devel] [PATCH pve-storage] fix #4165: disk: SMART: add normalized field Matthias Heiserer
2022-07-21 10:45 ` [pbs-devel] " Matthias Heiserer
2022-09-23 10:29 ` [pve-devel] applied: " Thomas Lamprecht
2022-09-23 10:29 ` [pbs-devel] applied: " Thomas Lamprecht
2022-07-21 10:45 ` [pve-devel] [PATCH widget-toolkit] fix #4165: SMART: use changed columns from the API Matthias Heiserer
2022-07-21 10:45 ` [pbs-devel] " Matthias Heiserer
2022-09-22 10:35 ` [pve-devel] [PATCH proxmox-backup] fix #4165: SMART: add raw field Dominik Csapak
2022-09-22 10:35 ` [pbs-devel] " Dominik Csapak
2022-09-23 10:31 ` [pve-devel] [pbs-devel] " Thomas Lamprecht
2022-09-23 10:31 ` [pbs-devel] [pve-devel] " Thomas Lamprecht
2022-09-23 10:28 ` Thomas Lamprecht [this message]
2022-09-23 10:28 ` [pbs-devel] applied: " Thomas Lamprecht
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=0cec4592-8711-a9fd-09a7-6ab0028b58fc@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.heiserer@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-devel@lists.proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal