From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied: [PATCH access-control v2] api, auth: fix two typos in user-visible description
Date: Fri, 22 Nov 2024 15:45:49 +0100 [thread overview]
Message-ID: <e5471ed0-3984-4d7b-8573-cec163f0d7d3@proxmox.com> (raw)
In-Reply-To: <20241122102627.521873-1-c.heiss@proxmox.com>
Am 22.11.24 um 11:25 schrieb Christoph Heiss:
> Just two small typos in user-visible API/schema description. Fix them
> up.
>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> v1: https://lore.proxmox.com/pve-devel/20241021120626.1293427-1-c.heiss@proxmox.com/
>
> Changes v1 -> v2:
> * rebased on latest master
>
> src/PVE/API2/AccessControl.pm | 2 +-
> src/PVE/Auth/Plugin.pm | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-22 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 10:25 [pve-devel] " Christoph Heiss
2024-11-22 14:45 ` 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=e5471ed0-3984-4d7b-8573-cec163f0d7d3@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@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