From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Lendl <s.lendl@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 pve-docs 0/6] sdn: Documentation
Date: Sat, 18 Nov 2023 17:51:26 +0100 [thread overview]
Message-ID: <8ad0026c-f21c-4ab1-a751-2f573b9b9d10@proxmox.com> (raw)
In-Reply-To: <20231117135531.3198353-1-s.lendl@proxmox.com>
Am 17/11/2023 um 14:55 schrieb Stefan Lendl:
> * Try to homogenize style and format
> * Title case naming conventions for configuration options
> * Simplify examples
> * Re-phrase descriptions
>
> Changes to v1 -> v2:
>
> * Split changes per chapter.
> * Use multi-line heading format like in the original file.
> I used search and replace to "revert" and now the format is identical on all
> headings.
and never tested even a simple build... just great...
asciidoc: ERROR: .asciidoc-pve-tmp4086737_pvesdn.adoc: line 912: [blockdef-listing] missing closing delimiter
aciidoc error at ./asciidoc-pve line 424.
make[3]: *** [pve-doc-generator.mk:75: chapter-pvesdn.html] Error 1
make[3]: *** Waiting for unfinished jobs....
asciidoc: ERROR: pvesdn.adoc: line 914: [blockdef-listing] missing closing delimiter
make[3]: *** [Makefile:140: pve-admin-guide.pdf] Error 1
asciidoc: ERROR: pvesdn.adoc: line 914: [blockdef-listing] missing closing delimiter
make[3]: *** [Makefile:146: pve-admin-guide.epub] Error 1
asciidoc: ERROR: pvesdn.adoc: line 914: [blockdef-listing] missing closing delimiter
Maybe check the diff and ensuring that the headings stay untouched would
help, the underline aligned with the width of the heading text for a reason..
Or well, a simple build test before sending this, that's the bare minimum that
I expect!
>
> Stefan Lendl (6):
> sdn: installation, overview and main configuration
> sdn: Zones
> sdn: VNets and Subnets
> sdn: Controllers
> sdn: IPAM
> sdn: Examples
>
those subjects are borderline useless, there's at least a verb missing.
> pvesdn.adoc | 906 +++++++++++++++++++++++-----------------------------
> 1 file changed, 402 insertions(+), 504 deletions(-)
>
next prev parent reply other threads:[~2023-11-18 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 13:55 Stefan Lendl
2023-11-17 13:55 ` [pve-devel] [PATCH v2 pve-docs 1/6] sdn: installation, overview and main configuration Stefan Lendl
2023-11-17 13:55 ` [pve-devel] [PATCH v2 pve-docs 2/6] sdn: Zones Stefan Lendl
2023-11-17 13:55 ` [pve-devel] [PATCH v2 pve-docs 3/6] sdn: VNets and Subnets Stefan Lendl
2023-11-17 13:55 ` [pve-devel] [PATCH v2 pve-docs 4/6] sdn: Controllers Stefan Lendl
2023-11-17 13:55 ` [pve-devel] [PATCH v2 pve-docs 5/6] sdn: IPAM Stefan Lendl
2023-11-17 13:55 ` [pve-devel] [PATCH v2 pve-docs 6/6] sdn: Examples Stefan Lendl
2023-11-18 16:51 ` Thomas Lamprecht [this message]
2023-11-20 8:48 ` [pve-devel] applied: [PATCH v2 pve-docs 0/6] sdn: Documentation 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=8ad0026c-f21c-4ab1-a751-2f573b9b9d10@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.lendl@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