From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 4/5] makefile: fix waring typo
Date: Wed, 17 Jul 2024 14:16:49 +0200 [thread overview]
Message-ID: <20240717121650.1466107-4-m.sandoval@proxmox.com> (raw)
In-Reply-To: <20240717121650.1466107-1-m.sandoval@proxmox.com>
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
bin/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bin/Makefile b/bin/Makefile
index 180a91b5..82d5c633 100644
--- a/bin/Makefile
+++ b/bin/Makefile
@@ -68,7 +68,7 @@ pve7to8.1:
printf ".TH PVE7TO8 1\n.SH NAME\npve7to8 \- Proxmox VE upgrade checker script for 7.4+ to current 8.x\n" > $@.tmp
printf ".SH DESCRIPTION\nThis tool will help you to detect common pitfalls and misconfguration\
before, and during the upgrade of a Proxmox VE system\n" >> $@.tmp
- printf "Any failure must be addressed before the upgrade, and any waring must be addressed, \
+ printf "Any failure must be addressed before the upgrade, and any warning must be addressed, \
or at least carefully evaluated, if a false-positive is suspected\n" >> $@.tmp
printf ".SH SYNOPSIS\npve7to8 [--full]\n" >> $@.tmp
mv $@.tmp $@
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-07-17 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 12:16 [pve-devel] [PATCH manager 1/5] fix typos in comments Maximiliano Sandoval
2024-07-17 12:16 ` [pve-devel] [PATCH manager 2/5] ui: ceph: rename wizzard variable to wizard Maximiliano Sandoval
2024-07-17 12:16 ` [pve-devel] [PATCH manager 3/5] guest import: fix attaced typo in translatable string Maximiliano Sandoval
2024-07-17 12:16 ` Maximiliano Sandoval [this message]
2024-07-17 12:16 ` [pve-devel] [PATCH manager 5/5] ceph: osd: fix canot typo Maximiliano Sandoval
2024-07-22 16:35 ` [pve-devel] applied-series: [PATCH manager 1/5] fix typos in comments 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=20240717121650.1466107-4-m.sandoval@proxmox.com \
--to=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 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.