| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | The pgperltidy diffs in HEAD |
| Date: | 2025-11-25 14:50:01 |
| Message-ID: | A0C626D2-5B57-4E65-9731-080A2E2AD015@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| pgperltidy_20251125.diff | application/octet-stream | 21.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2025-11-25 14:55:12 | Re: PRI?64 vs Visual Studio (2022) |
| Previous Message | Peter Eisentraut | 2025-11-25 14:46:39 | Re: backend/nodes cleanup: Move loop variables definitions into for statement |