public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] tree-wide: properly use {pve} instead of PVE
Date: Tue, 6 Jun 2023 16:51:11 +0200	[thread overview]
Message-ID: <1024f46c-4525-d42d-0452-2a2af8781194@proxmox.com> (raw)
In-Reply-To: <20230328120357.1358052-1-f.gruenbichler@proxmox.com>

Am 28/03/2023 um 14:03 schrieb Fabian Grünbichler:
> where applicable, or expand/replace where it's not a good fit or automatic
> expansion doesn't work.
> 
> there are a few more in generated files, those need to be cleaned up
> separately.
> 
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> 
> Notes:
>     specifically, HA resources has \{pve\}, where the perl schema doesn't have the
>     back slashes, so somewhere in the formatting code escaping happens when it
>     shouldn't, but removing the escaping might break something else..
>     
>     pve-access-control has a few bare PVE instances in the LDAP schema, and one in
>     a deprecation note "PVE-8.0" in PVE::API2::AccessControl.
> 
>  getting-help.adoc      | 4 ++--
>  pmxcfs.adoc            | 4 ++--
>  pve-firewall.adoc      | 2 +-
>  pve-package-repos.adoc | 2 +-
>  pvesm.adoc             | 2 +-
>  pvesr.adoc             | 6 +++---
>  6 files changed, 10 insertions(+), 10 deletions(-)
> 
>

applied, thanks!




      reply	other threads:[~2023-06-06 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 12:03 [pve-devel] " Fabian Grünbichler
2023-06-06 14:51 ` 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=1024f46c-4525-d42d-0452-2a2af8781194@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal