From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager v2] fix typos in user visible strings
Date: Wed, 16 Oct 2024 18:42:03 +0200 [thread overview]
Message-ID: <6e5d6b8a-1654-4768-aba8-b292e6f92e44@proxmox.com> (raw)
In-Reply-To: <20241014133945.261667-1-m.sandoval@proxmox.com>
Am 14/10/2024 um 15:39 schrieb Maximiliano Sandoval:
> Found with the `typos` cli tool.
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
>
> Differences from v1:
> - Do not fix `state = 'uknown'` typo. It is not user facing
> - Fix commit message
>
> www/manager6/ceph/CephInstallWizard.js | 2 +-
> www/manager6/node/Certificates.js | 2 +-
> www/mobile/Toolkit.js | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-10-16 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:39 [pve-devel] " Maximiliano Sandoval
2024-10-16 16:42 ` Thomas Lamprecht [this message]
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=6e5d6b8a-1654-4768-aba8-b292e6f92e44@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox