Re: Add trim_trailing_whitespace to editorconfig file
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Daniel Gustafsson <daniel@yesql.se>,
Melanie Plageman <melanieplageman@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-02-16T10:44:56Z
Lists: pgsql-hackers
v3-0001-Remove-non-existing-file-from-.gitattributes.patch I have committed that one. v3-0002-Require-final-newline-in-.po-files.patch The .po files are imported from elsewhere, so I'm not sure this is going to have the desired effect. Perhaps it's worth cleaning up, but it would require more steps. v3-0003-Bring-editorconfig-in-line-with-gitattributes.patch I question whether we need to add rules to .editorconfig about files that are generated or imported from elsewhere, since those are not meant to be edited.
Commits
-
Add script to keep .editorconfig in sync with .gitattributes
- 2452e71ff2fe 18.0 landed
-
Remove non-existing file from .gitattributes
- 1d577f2eaa88 15.7 landed
- 2c7f2eb0c8aa 16.3 landed
- e85732dac0e9 17.0 landed