From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 024451FF17A for ; Tue, 25 Nov 2025 12:14:14 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 96B5114359; Tue, 25 Nov 2025 12:14:24 +0100 (CET) Date: Tue, 25 Nov 2025 20:13:37 +0900 To: Proxmox VE development discussion References: <20251117164756.432508-1-s.sterz@proxmox.com> <176339946305.3864094.11466727722226385250.b4-ty@proxmox.com> In-Reply-To: MIME-Version: 1.0 Message-ID: List-Id: Proxmox VE development discussion List-Post: From: ribbon via pve-devel Precedence: list Cc: ribbon X-Mailman-Version: 2.1.29 X-BeenThere: pve-devel@lists.proxmox.com List-Subscribe: , List-Unsubscribe: , List-Archive: Reply-To: Proxmox VE development discussion List-Help: Subject: Re: [pve-devel] Typo? Content-Type: multipart/mixed; boundary="===============7233487570317200131==" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" --===============7233487570317200131== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: X-Original-To: pve-devel@lists.proxmox.com Delivered-To: pve-devel@lists.proxmox.com Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id DA98AD1347 for ; Tue, 25 Nov 2025 12:14:23 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B52F6142E7 for ; Tue, 25 Nov 2025 12:13:53 +0100 (CET) Received: from ns.ribbon.or.jp (unknown [210.171.174.178]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 25 Nov 2025 12:13:52 +0100 (CET) Received: by ns.ribbon.or.jp (Postfix, from userid 1001) id A17A83C01CD; Tue, 25 Nov 2025 20:13:37 +0900 (JST) Date: Tue, 25 Nov 2025 20:13:37 +0900 From: ribbon To: Proxmox VE development discussion Subject: Re: [pve-devel] Typo? Message-ID: References: <20251117164756.432508-1-s.sterz@proxmox.com> <176339946305.3864094.11466727722226385250.b4-ty@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) X-SPAM-LEVEL: Spam detection results: 1 AWL -1.096 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_NONE 0.1 DMARC none policy KAM_DMARC_NONE 0.25 DKIM has Failed or SPF has failed on the message and the domain has no DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods KAM_LINKBAIT 2.5 Short messages containing little more than a link, from a domain with no security in place RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record WEIRD_PORT 0.001 Uses non-standard port number for HTTP I found the following content in ja.po. Could this be a typo? #: proxmox-yew-comp/src/form/pve/lxc_property/mod.rs:179 #, fuzzy msgid "Hostame" ribbon --===============7233487570317200131== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel --===============7233487570317200131==--