From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs/qemu-server/manager] improving docs & consistency for ova/ovf import
Date: Tue, 19 Nov 2024 09:39:54 +0100 [thread overview]
Message-ID: <20241119083958.513287-1-d.csapak@proxmox.com> (raw)
adding docs section, unifying wording and adding help button to the
import wizard
pve-docs:
Dominik Csapak (1):
qm: adapt import section to newly added OVA/OVF import
qm.adoc | 35 ++++++++++++++++++++++++++++-------
1 file changed, 28 insertions(+), 7 deletions(-)
qemu-server:
Dominik Csapak (1):
api: import working storage: improve error message
PVE/API2/Qemu.pm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
pve-manager:
Dominik Csapak (2):
ui: import: add onlineHelp reference
ui: import: clarify working storage emptyText
www/manager6/window/GuestImport.js | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-11-19 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 8:39 Dominik Csapak [this message]
2024-11-19 8:39 ` [pve-devel] [PATCH docs 1/1] qm: adapt import section to newly added OVA/OVF import Dominik Csapak
2024-11-19 8:39 ` [pve-devel] [PATCH qemu-server 1/1] api: import working storage: improve error message Dominik Csapak
2024-11-19 8:39 ` [pve-devel] [PATCH manager 1/2] ui: import: add onlineHelp reference Dominik Csapak
2024-11-19 8:39 ` [pve-devel] [PATCH manager 2/2] ui: import: clarify working storage emptyText Dominik Csapak
2024-11-19 16:00 ` [pve-devel] applied-series: [PATCH docs/qemu-server/manager] improving docs & consistency for ova/ovf import 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=20241119083958.513287-1-d.csapak@proxmox.com \
--to=d.csapak@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.