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:-series [PATCH access-control 0/3] fix undef warning on login for case-insensitive realms
Date: Fri, 4 Apr 2025 18:55:29 +0200 [thread overview]
Message-ID: <5a58caac-189d-4f1b-bb39-0f28ad24a7b1@proxmox.com> (raw)
In-Reply-To: <20250325104053.491601-1-c.heiss@proxmox.com>
Am 25.03.25 um 11:38 schrieb Christoph Heiss:
> This primarily fixes a Perl warning in the syslog about a undef
> variable, with no impact on the actual functionality though.
>
> The two other patches #2 and #3 just clean up some small things I came
> across while at it.
>
> Christoph Heiss (3):
> access: lookup: fix undef warning for case-insensitive realms
> access: lookup: avoid reading user.cfg from cfs unnecessarily
> gitignore: add rules for dpkg build artifacts
>
> .gitignore | 7 +++++++
> src/PVE/AccessControl.pm | 4 ++--
> 2 files changed, 9 insertions(+), 2 deletions(-)
>
applied series, 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:[~2025-04-04 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 10:38 [pve-devel] " Christoph Heiss
2025-03-25 10:38 ` [pve-devel] [PATCH access-control 1/3] access: lookup: fix undef warning " Christoph Heiss
2025-03-25 10:38 ` [pve-devel] [PATCH access-control 2/3] access: lookup: avoid reading user.cfg from cfs unnecessarily Christoph Heiss
2025-03-25 10:38 ` [pve-devel] [PATCH access-control 3/3] gitignore: add rules for dpkg build artifacts Christoph Heiss
2025-04-04 16:55 ` 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=5a58caac-189d-4f1b-bb39-0f28ad24a7b1@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal