From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH proxmox-perltidy] use more explicit --cuddled-blocks rather than --cuddled-else
Date: Mon, 30 Mar 2026 12:45:56 +0200 [thread overview]
Message-ID: <177486755417.1648851.6854812050346785317.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260327132234.123474-1-f.ebner@proxmox.com>
On Fri, 27 Mar 2026 14:17:08 +0100, Fiona Ebner wrote:
> The --cuddled-else flag is equivalent to --cuddled-blocks, but might
> wrongly suggest that it only applies to else (and elsif). While those
> are the most relevant ones for the Proxmox codebases, there are a few
> other ones (see 'man perltidy'). Using --cuddled-blocks also better
> suggests that the --cuddled-block-list option is a modifier that only
> takes effect when --cuddled-blocks itself is present.
>
> [...]
Applied, thanks!
[1/1] use more explicit --cuddled-blocks rather than --cuddled-else
commit: 87fd746b7e083021dfe9bb7801931bf74b436464
prev parent reply other threads:[~2026-03-30 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 13:17 Fiona Ebner
2026-03-30 10: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=177486755417.1648851.6854812050346785317.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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