From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 0/2] bin: auto-format code using perltidy
Date: Mon, 7 Jul 2025 13:01:35 +0200 [thread overview]
Message-ID: <20250707110146.800467-1-c.heiss@proxmox.com> (raw)
Reformats all Perl scripts in bin/ with perltidy using Proxmox style
guides, as was done in commit 138cae897 for all other Perl code.
As these files do not use `.pl` or `.pm` as file extensions, they were
missed during the initial reformatting.
Patch #1 just adds the appropriate make target, patch #2 runs exactly
that.
Christoph Heiss (2):
buildsys: add target for auto-formatting bin/ scripts
bin: auto-format code using perltidy with Proxmox style guide
Makefile | 1 +
bin/Makefile | 4 +
bin/pve-init-ceph-crash | 127 +++++++++++++-------------
bin/pvebanner | 2 +-
bin/pvedaemon | 2 +-
bin/pveperf | 198 ++++++++++++++++++++--------------------
bin/pveproxy | 10 +-
bin/pvereport | 2 +-
bin/pveupdate | 118 +++++++++++++-----------
bin/pveupgrade | 36 ++++----
bin/pveversion | 37 ++++----
bin/spiceproxy | 12 +--
12 files changed, 280 insertions(+), 269 deletions(-)
--
2.49.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-07 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 11:01 Christoph Heiss [this message]
2025-07-07 11:01 ` [pve-devel] [PATCH manager 1/2] buildsys: add target for auto-formatting bin/ scripts Christoph Heiss
2025-07-07 18:52 ` [pve-devel] applied: " Thomas Lamprecht
2025-07-07 11:01 ` [pve-devel] [PATCH manager 2/2] bin: auto-format code using perltidy with Proxmox style guide Christoph Heiss
2025-07-07 11:23 ` [pve-devel] [PATCH manager 0/2] bin: auto-format code using perltidy Thomas Lamprecht
2025-07-07 11:44 ` Christoph Heiss
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=20250707110146.800467-1-c.heiss@proxmox.com \
--to=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