From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id C49CE1FF161 for ; Wed, 20 Nov 2024 19:24:20 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 759C315E72; Wed, 20 Nov 2024 19:24:25 +0100 (CET) From: Daniel Kral To: pve-devel@lists.proxmox.com Date: Wed, 20 Nov 2024 19:24:14 +0100 Message-Id: <20241120182414.125789-3-d.kral@proxmox.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20241120182414.125789-1-d.kral@proxmox.com> References: <20241120182414.125789-1-d.kral@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [options.rs] Subject: [pve-devel] [PATCH installer 3/3] common: make btrfs disk options uppercase for consistency X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" As XFS and ZFS are spelled in uppercase letters in the installer UI and BTRFS is usually written in this way too, make the BTRFS string uppercase too for consistency wrt to the other options. Signed-off-by: Daniel Kral --- I just noticed this while booting up the PVE installer and as it (vaguely) fits with the theme of this patch series, let's also make the bootdisk option in the GUI/TUI consistent wrt to the others. proxmox-installer-common/src/options.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proxmox-installer-common/src/options.rs b/proxmox-installer-common/src/options.rs index 58fadf8..37e6260 100644 --- a/proxmox-installer-common/src/options.rs +++ b/proxmox-installer-common/src/options.rs @@ -69,7 +69,7 @@ impl fmt::Display for FsType { FsType::Ext4 => write!(f, "ext4"), FsType::Xfs => write!(f, "XFS"), FsType::Zfs(level) => write!(f, "ZFS ({level})"), - FsType::Btrfs(level) => write!(f, "Btrfs ({level})"), + FsType::Btrfs(level) => write!(f, "BTRFS ({level})"), } } } -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel