From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] gui: document tags with screenshots
Date: Fri, 18 Nov 2022 16:23:29 +0100 [thread overview]
Message-ID: <5e8dc6e8-b644-7298-192b-d0d846aa3b7c@proxmox.com> (raw)
In-Reply-To: <20221118112922.2206811-1-d.csapak@proxmox.com>
Am 18/11/2022 um 12:29 schrieb Dominik Csapak:
> and list some examples
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> was a bit restricted by the space for screenshots, so i only really
> could add three here. when i added more i couldn't get the spacing
> right.
>
> also needs the screenshots applied to the repo to be buildable
> @thomas will do that
>
> pve-gui.adoc | 69 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 69 insertions(+)
>
>
applied, thanks!
prev parent reply other threads:[~2022-11-18 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 11:29 [pve-devel] " Dominik Csapak
2022-11-18 15:23 ` 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=5e8dc6e8-b644-7298-192b-d0d846aa3b7c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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