From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs 3/3] pveceph: ec pool: add note about parameter usage on creation
Date: Wed, 4 May 2022 07:56:23 +0200 [thread overview]
Message-ID: <12b3322d-17d2-ddb6-6a25-7b0833d41b1d@proxmox.com> (raw)
In-Reply-To: <20220503115809.2566406-4-a.lauterer@proxmox.com>
Am 5/3/22 um 13:58 schrieb Aaron Lauterer:
> Some optional parameters will only be used for the replicated metadata
> pool.
>
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> pveceph.adoc | 6 ++++++
> 1 file changed, 6 insertions(+)
>
>
applied, thanks!
FYI: i did a s/'/`/ on the whole EC section, as those are all not file path's I'd guess,
and we normally use the `foo` syntax for parameters and special values in asciidoc.
https://powerman.name/doc/asciidoc#_text
Also added a separate create/add headings below introduction about EC for slightly more
document structure.
next prev parent reply other threads:[~2022-05-04 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 11:58 [pve-devel] [PATCH manager/docs 0/3] EC follow ups Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH manager 1/3] ceph pools create: remove crush_rule for ec pool data Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH manager 2/3] ceph pools create: enhance erasure-code description Aaron Lauterer
2022-05-03 11:58 ` [pve-devel] [PATCH docs 3/3] pveceph: ec pool: add note about parameter usage on creation Aaron Lauterer
2022-05-04 5:56 ` Thomas Lamprecht [this message]
2022-05-04 5:56 ` [pve-devel] applied-series: [PATCH manager/docs 0/3] EC follow ups 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=12b3322d-17d2-ddb6-6a25-7b0833d41b1d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@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