From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 docs] pct: clarify simple restore mode default 'local' storage
Date: Thu, 23 Sep 2021 13:09:03 +0200 [thread overview]
Message-ID: <1632395327.3zd1u56vem.astroid@nora.none> (raw)
In-Reply-To: <20210922111242.588631-1-o.bektas@proxmox.com>
with a small follow-up.
On September 22, 2021 1:12 pm, Oguz Bektas wrote:
> "default local storage" is confusing without the backticks. reword the
> sentences to make it clearer about `storage` parameter usage.
>
> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> ---
> pct.adoc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/pct.adoc b/pct.adoc
> index c5ed243..9a9d4ff 100644
> --- a/pct.adoc
> +++ b/pct.adoc
> @@ -792,8 +792,8 @@ explicitly set, the mount point configuration from the backed up configuration
> file is restored using the following steps:
>
> . Extract mount points and their options from backup
> -. Create volumes for storage backed mount points (on storage provided with the
> - `storage` parameter, or default local storage if unset)
> +. Create volumes for storage backed mount points on the target provided with the
> + `storage` parameter. (default: `local`)
> . Extract files from backup archive
> . Add bind and device mount points to restored configuration (limited to root
> user)
> --
> 2.30.2
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
>
prev parent reply other threads:[~2021-09-23 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 11:12 [pve-devel] " Oguz Bektas
2021-09-23 11:09 ` Fabian Grünbichler [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=1632395327.3zd1u56vem.astroid@nora.none \
--to=f.gruenbichler@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.