From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 1/2] buildsys: add target for auto-formatting bin/ scripts
Date: Mon, 7 Jul 2025 13:01:36 +0200 [thread overview]
Message-ID: <20250707110146.800467-2-c.heiss@proxmox.com> (raw)
In-Reply-To: <20250707110146.800467-1-c.heiss@proxmox.com>
Much in the same way as the top-level target.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Makefile | 1 +
bin/Makefile | 4 ++++
2 files changed, 5 insertions(+)
diff --git a/Makefile b/Makefile
index b05d5e129..eb1425222 100644
--- a/Makefile
+++ b/Makefile
@@ -18,6 +18,7 @@ all: $(SUBDIRS)
.PHONY: tidy
tidy:
git ls-files ':*.p[ml]'| xargs -n4 -P0 proxmox-perltidy
+ $(MAKE) -C bin tidy
.PHONY: check
check: bin test www
diff --git a/bin/Makefile b/bin/Makefile
index caed0af4b..3931804b1 100644
--- a/bin/Makefile
+++ b/bin/Makefile
@@ -81,6 +81,10 @@ pveversion.1.pod: pveversion
pveupgrade.1.pod: pveupgrade
pvereport.1.pod: pvereport
+.PHONY: tidy
+tidy:
+ echo $(SCRIPTS) $(HELPERS) | xargs -n4 -P0 proxmox-perltidy
+
.PHONY: check
check: $(addsuffix .service-api-verified, $(SERVICES)) $(addsuffix .api-verified, $(CLITOOLS))
rm -f *.service-api-verified *.api-verified
--
2.49.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent 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 [pve-devel] [PATCH manager 0/2] bin: auto-format code using perltidy Christoph Heiss
2025-07-07 11:01 ` Christoph Heiss [this message]
2025-07-07 18:52 ` [pve-devel] applied: [PATCH manager 1/2] buildsys: add target for auto-formatting bin/ scripts 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-2-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 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.