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 v2 docs] pvecm: add qdevice status flag explanation
Date: Tue, 25 Jul 2023 17:21:55 +0200 [thread overview]
Message-ID: <3cb48274-7023-41ed-895d-4cb03ac34924@proxmox.com> (raw)
In-Reply-To: <20230725110003.3728126-1-a.lauterer@proxmox.com>
On 25/07/2023 13:00, Aaron Lauterer wrote:
> They are underdocumented and finding information is not that easy.
>
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> changes:
> * added reference anchor for easier linking
> * use link to manpages.debian.org instead of github
>
>
> the corosync-doc package does ship HTML documentation, but no man pages,
> therefore only the link
>
> pvecm.adoc | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
>
applied but split the overly long footnote line (only xref ones need
to be a single line due to our limited parser, but footnotes aren't
looked for by it so there it doesn't matter), thanks!
prev parent reply other threads:[~2023-07-25 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 11:00 [pve-devel] " Aaron Lauterer
2023-07-25 15:21 ` 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=3cb48274-7023-41ed-895d-4cb03ac34924@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