public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Elias Huhsovitz <e.huhsovitz@proxmox.com>, d.csapak@proxmox.com
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH access-control] rpc: do not check malformed acl path
Date: Wed, 26 Aug 2026 15:03:52 +0200	[thread overview]
Message-ID: <792a093e-1f8b-4066-b6ec-f98f3cf3d292@proxmox.com> (raw)
In-Reply-To: <DKYW2BYYARKN.TGY2TKE46ONR@proxmox.com>

Am 26.08.26 um 2:53 PM schrieb Elias Huhsovitz:
> Thanks for the quick response!
> 
> This was intended as a repsonse to this review:
> https://lore.proxmox.com/pve-devel/8eff67e8-ac88-4b7d-a90d-de32644d1d95@proxmox.com/
> 
> I didn't mean for this to be a fully finished patch. This was meant
> as a follow up.

Yes, I saw. But ah okay, that's why there was no full commit message,
got it!

> I am unsure how to reply to a review while sharing code at
> the same time. I relied on `--in-reply-to=` paramter too much.
> 
> Sorry for the trouble!

No worries, this is fine :)

> But your input resolves my confusion, so thanks a lot! :)






  reply	other threads:[~2026-08-26 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 11:26 [PATCH manager] fix #6735: api: pci: extend mdevscan persmissions for mappings Elias Huhsovitz
2026-08-26  7:12 ` Dominik Csapak
2026-08-26 10:37   ` [PATCH access-control] rpc: do not check malformed acl path Elias Huhsovitz
2026-08-26 12:37     ` Fiona Ebner
2026-08-26 12:53       ` Elias Huhsovitz
2026-08-26 13:03         ` Fiona Ebner [this message]
2026-08-26 13:04     ` Dominik Csapak
2026-08-27 11:28 ` superseded: [PATCH manager] fix #6735: api: pci: extend mdevscan persmissions for mappings Elias Huhsovitz

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=792a093e-1f8b-4066-b6ec-f98f3cf3d292@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=e.huhsovitz@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