public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup 0/6] docs: cleanup and add certificate docs
Date: Mon, 16 May 2022 19:28:38 +0200	[thread overview]
Message-ID: <139ce39d-d407-c07e-6e52-de7898f61ab6@proxmox.com> (raw)
In-Reply-To: <20220516162733.62060-1-s.ivanov@proxmox.com>

Am 5/16/22 um 18:27 schrieb Stoiko Ivanov:
> while trying to add the certificate documentation I noticed a few
> (rather harmless) warnings while running make html
> 
> patches 1-3 address those and are independent of the certificate
> documentation (3-6).
> 
> For the certificate docs I took the approach of (semi) automatically
> converting the ssl-docs from pmg-docs to rst (asciidoc->docbook (via
> asciidoc), docbook->rst (via pandoc)) - the exact commands are
> in the commit message of 4/6.
> 
> The mid-term idea here would be to have one single source for the common
> docs (system-booting, local-zfs and parts of the certificate
> documentation come to mind for now) - since keeping them in multiple
> places, but with similar/identical content just means that improvments
> don't make it to all copies (or only with quite a bit of manual
> vimdiffing by the code-reviewers)
> 

applied, thanks!

But replaced the odd image-referencing with just placing them inline, and align
to a side plus add an alt text like we do for most others.
Also removed a duplicate usage of showing the challenge plugins screenshot.




      parent reply	other threads:[~2022-05-16 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 16:27 [pbs-devel] " Stoiko Ivanov
2022-05-16 16:27 ` [pbs-devel] [PATCH proxmox-backup 1/6] docs: silence duplicate label warnings Stoiko Ivanov
2022-05-16 16:27 ` [pbs-devel] [PATCH proxmox-backup 2/6] docs: cleanup and readd command-line-tools Stoiko Ivanov
2022-05-16 16:27 ` [pbs-devel] [PATCH proxmox-backup 3/6] docs: use case-matching keys for glossary Stoiko Ivanov
2022-05-16 16:27 ` [pbs-devel] [PATCH proxmox-backup 4/6] docs: add certificate-management.rst Stoiko Ivanov
2022-05-16 16:27 ` [pbs-devel] [PATCH proxmox-backup 5/6] docs: certificates Stoiko Ivanov
2022-05-16 16:27 ` [pbs-devel] [PATCH proxmox-backup 6/6] docs: certs: add screenshots Stoiko Ivanov
2022-05-16 17:28 ` 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=139ce39d-d407-c07e-6e52-de7898f61ab6@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=s.ivanov@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal