From: "Max R. Carrara" <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-storage v2 0/3] Improve mkpath Error Message in activate_storage
Date: Thu, 23 Apr 2026 11:46:13 +0200 [thread overview]
Message-ID: <20260423094619.205988-1-m.carrara@proxmox.com> (raw)
See the cover letter of v1 (linked below) for a description of this
series.
Changes since v1:
- Rebased on master (nothing changed)
- Clarified message of patch #2, as pointed out by Fiona [1] (thanks!)
- Improved the error matching done in patch #3 as suggested by Fabian [2]
(thanks!) and updated the commit message accordingly
Older Versions
==============
v1: https://lore.proxmox.com/pve-devel/20251205154404.446338-1-m.carrara@proxmox.com/
References
==========
[1]: https://lore.proxmox.com/pve-devel/60139202-64a0-4111-9773-a571ffde0389@proxmox.com/
[2]: https://lore.proxmox.com/pve-devel/1768487461.gbidzul2yw.astroid@yuna.none/
Summary of Changes
==================
Max R. Carrara (3):
plugin: use guard clause to reduce nesting
plugin: remove needless inequality check when creating content subdirs
plugin: improve error handling when creating a content subdir fails
src/PVE/Storage/Plugin.pm | 80 ++++++++++++++++++++++++++-------------
1 file changed, 54 insertions(+), 26 deletions(-)
--
2.47.3
next reply other threads:[~2026-04-23 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 9:46 Max R. Carrara [this message]
2026-04-23 9:46 ` [PATCH pve-storage v2 1/3] plugin: use guard clause to reduce nesting Max R. Carrara
2026-04-23 9:46 ` [PATCH pve-storage v2 2/3] plugin: remove needless inequality check when creating content subdirs Max R. Carrara
2026-04-23 9:46 ` [PATCH pve-storage v2 3/3] plugin: improve error handling when creating a content subdir fails Max R. Carrara
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=20260423094619.205988-1-m.carrara@proxmox.com \
--to=m.carrara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.