From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 1/2] storage: document import content type
Date: Fri, 9 Jan 2026 14:41:20 +0100 [thread overview]
Message-ID: <c39f7c35-8ee5-47cf-9c9d-825e54a66ffc@proxmox.com> (raw)
In-Reply-To: <20260108151106.861442-1-m.sandoval@proxmox.com>
Am 08.01.26 um 4:10 PM schrieb Maximiliano Sandoval:
> This content type is mentioned at [10.7].
>
> [10.7] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_import_virtual_machines.
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> pvesm.adoc | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/pvesm.adoc b/pvesm.adoc
> index d36baf8..7c1d795 100644
> --- a/pvesm.adoc
> +++ b/pvesm.adoc
> @@ -232,6 +232,10 @@ snippets:::
>
> Snippet files, for example guest hook scripts
>
> +import:::
> +
> +Allows importing VM disk images
The other descriptions all mention 'what' the content is. Well, except
'rootdir', but that should also be changed IMHO. Playing the devil's
advocate, what you wrote could also be interpreted as 'if I select
import content type, then I can import to that storage'.
> +
> shared::
>
> Indicate that this is a single storage with the same contents on all nodes (or
_______________________________________________
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:[~2026-01-09 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 15:11 Maximiliano Sandoval
2026-01-08 15:11 ` [pve-devel] [PATCH docs 2/2] storage: document import content path Maximiliano Sandoval
2026-01-09 13:47 ` [pve-devel] applied: " Fiona Ebner
2026-01-09 13:41 ` Fiona Ebner [this message]
2026-01-09 14:18 ` [pve-devel] applied: [PATCH docs 1/2] storage: document import content type Fiona Ebner
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=c39f7c35-8ee5-47cf-9c9d-825e54a66ffc@proxmox.com \
--to=f.ebner@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