all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 3/3] pvereport: code cleanup, line length
Date: Mon, 21 Dec 2020 16:13:51 +0100	[thread overview]
Message-ID: <20201221151351.30575-3-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20201221151351.30575-1-a.lauterer@proxmox.com>

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
 PVE/Report.pm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/PVE/Report.pm b/PVE/Report.pm
index f8d5e663..228fbb29 100644
--- a/PVE/Report.pm
+++ b/PVE/Report.pm
@@ -73,7 +73,8 @@ my $init_report_cmds = sub {
 	],
     };
 
-    push @{$report_def->{volumes}}, 'zpool status', 'zpool list -v', 'zfs list' if cmd_exists('zfs');
+    push @{$report_def->{volumes}}, 'zpool status', 'zpool list -v', 'zfs list'
+	if cmd_exists('zfs');
 
     if (-e '/etc/ceph/ceph.conf') {
 	# TODO: add (now working) rdb ls over all pools? really needed?
-- 
2.20.1





  parent reply	other threads:[~2020-12-21 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 15:13 [pve-devel] [PATCH manager 1/3] pvereport: fix multipath inclusion Aaron Lauterer
2020-12-21 15:13 ` [pve-devel] [PATCH manager 2/3] pvereport: rework report contents Aaron Lauterer
2020-12-21 16:06   ` [pve-devel] applied: " Thomas Lamprecht
2020-12-21 16:15   ` [pve-devel] " Thomas Lamprecht
2020-12-21 15:13 ` Aaron Lauterer [this message]
2020-12-21 16:08   ` [pve-devel] applied: Re: [PATCH manager 3/3] pvereport: code cleanup, line length Thomas Lamprecht
2020-12-21 16:02 ` [pve-devel] applied: Re: [PATCH manager 1/3] pvereport: fix multipath inclusion 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=20201221151351.30575-3-a.lauterer@proxmox.com \
    --to=a.lauterer@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