| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Arseniy Mukhin <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: [PATCH] pg_bsd_indent: improve formatting of multiline comments |
| Date: | 2025-12-11 21:48:27 |
| Message-ID: | aTs8K_okt9MfEnP0@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
With the latest patch applied, I'm still seeing problems with **** and ====
lines in aclcheck.c and analyze.c, as mentioned upthread [0]. I think we
should also figure out what we want to do for things like this:
******************************************************************************
- This file contains routines that can be bound to a Postgres backend and
- called by the backend in the process of processing queries. The calling
- format for these routines is dictated by Postgres architecture.
+ * This file contains routines that can be bound to a Postgres backend and
+ * called by the backend in the process of processing queries. The calling
+ * format for these routines is dictated by Postgres architecture.
******************************************************************************/
Could we modify the patch to leave these kinds of comments alone?
[0] https://postgr.es/m/aP-H6kSsGOxaB21k%40nathan
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2025-12-11 21:52:26 | Re: Extended Statistics set/restore/clear functions. |
| Previous Message | Nathan Bossart | 2025-12-11 21:43:31 | Re: [PATCH] pg_bsd_indent: improve formatting of multiline comments |