From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Daniel Kral <d.kral@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs 1/3] storage: make description of storage CLI examples more consistent
Date: Mon, 7 Apr 2025 15:22:02 +0200 [thread overview]
Message-ID: <174403211151.2829243.15032011164980653418.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250304100915.55114-1-d.kral@proxmox.com>
On Tue, 04 Mar 2025 11:09:13 +0100, Daniel Kral wrote:
> Make the text for `pvesm scan` and `pvesm add` command examples more
> consistent by introducing `pvesm scan` with "You can get ... with", as
> it is already done for other storage plugins, and changing from past
> tense to present tense in existing descriptions for the `pvesm add` as
> recommended in the Technical Writing Style Guide for instructions [0].
>
> While at it, replace the term "share" with the more appropriate
> "datastore" for the example in the PBS section.
>
> [...]
Applied, thanks!
[1/3] storage: make description of storage CLI examples more consistent
commit: 500faf074374a962e26581b8e232caef02c600cf
[2/3] storage: change to newer pvesm scan subcommands in examples
commit: 28eb02fb33cfaaae47689f0515f13c91568b1740
[3/3] storage: add remaining pvesm scan command examples
commit: 528fe5d7f39ccae0d3ce636beb82ca4167fadc2b
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-04-07 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:09 [pve-devel] " Daniel Kral
2025-03-04 10:09 ` [pve-devel] [PATCH docs 2/3] storage: change to newer pvesm scan subcommands in examples Daniel Kral
2025-03-04 10:09 ` [pve-devel] [PATCH docs 3/3] storage: add remaining pvesm scan command examples Daniel Kral
2025-04-07 13:22 ` 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=174403211151.2829243.15032011164980653418.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.kral@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal