From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Markus Frank <m.frank@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: [pve-devel] applied: [PATCH storage] changed regex to allow @ in directory storage paths
Date: Wed, 7 Jun 2023 09:14:18 +0200 [thread overview]
Message-ID: <37onua7fnwwc4vb6kngn4jxifaqvk76ykoujlwrpfmztojdlj7@ryzarh2vhgrv> (raw)
In-Reply-To: <20230427120445.119419-1-m.frank@proxmox.com>
applied, thanks
once we can be sure there are no bad `system("foo $path bar");` calls
anywhere we might be able to drop this check entirely...
some day...
prev parent reply other threads:[~2023-06-07 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 12:04 [pve-devel] " Markus Frank
2023-06-07 7:14 ` Wolfgang Bumiller [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=37onua7fnwwc4vb6kngn4jxifaqvk76ykoujlwrpfmztojdlj7@ryzarh2vhgrv \
--to=w.bumiller@proxmox.com \
--cc=m.frank@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