The pgperltidy diffs in HEAD

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

To: Pgsql Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-11-25T14:50:01Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Check for correct version of perltidy
- 1cdb84bb1bcd 19 (unreleased) landed

Attachments

pgperltidy_20251125.diff (application/octet-stream) patch

I routinely run pgperltidy src/ when hacking on things, and am greeted with
lots of diffs like how pgindent runs used to be.  Are there objections to
applying the diffs we've accumulated so far with a .git-blame-ignore-revs
update alongside it? Are there reasons not that I am missing?

Attached is the current output from pgperltidy, I haven't looked over it in
detail but I am happy to take that on assuming it's not objected to.

--
Daniel Gustafsson