Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Phase 2 of pgindent updates. | Tom Lane | 2017-06-21 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change pg_bsd_indent to follow upstream rules for placement of comments to the right of code, and remove pgindent hack that caused comments following #endif to not obey the general rule. Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using the published version of pg_bsd_indent, but a hacked-up version that tried to minimize the amount of movement of comments to the right of code. The situation of interest is where such a comment has to be moved to the right of its default placement at column 33 because there's code there. BSD indent has always moved right in units of tab stops in such cases --- but in the previous incarnation, indent was working in 8-space tab stops, while now it knows we use 4-space tabs. So the net result is that in about half the cases, such comments are placed one tab stop left of before. This is better all around: it leaves more room on the line for comment text, and it means that in such cases the comment uniformly starts at the next 4-space tab stop after the code, rather than sometimes one and sometimes two tabs after. Also, ensure that comments following #endif are indented the same as comments following other preprocessor commands such as #else. That inconsistency turns out to have been self-inflicted damage from a poorly-thought-through post-indent "fixup" in pgindent. This patch is much less interesting than the first round of indent changes, but also bulkier, so I thought it best to separate the effects. Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us | ||
* | With ecpg exclusion removed, re-run pgindent for 9.4 | Bruce Momjian | 2014-05-06 |
| | | | | Report by Tom Lane | ||
* | Revert pgindent changes to ecpg include files that are part of ecpg | Bruce Momjian | 2010-02-26 |
| | | | | | regession test output, and update pgindent script to avoid them in the future. | ||
* | pgindent run for 9.0 | Bruce Momjian | 2010-02-26 |
| | |||
* | Ah, should read the file completely. I got so used to git that I almost ↵ | Michael Meskes | 2010-01-05 |
| | | | | forgot about the cvs stuff. | ||
* | Applied patch by Boszormenyi Zoltan <zb@cybertec.at> to add sqlda support to | Michael Meskes | 2010-01-05 |
| | | | | ecpg in both native and compatiblity mode. | ||
* | 8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list | Bruce Momjian | 2009-06-11 |
| | | | | provided by Andrew. | ||
* | Add $PostgreSQL$ markers to a lot of files that were missing them. | Andrew Dunstan | 2008-05-17 |
| | | | | | | | | | | This particular batch was just for *.c and *.h file. The changes were made with the following 2 commands: find . \( \( -name 'libstemmer' -o -name 'expected' -o -name 'ppport.h' \) -prune \) -o \( -name '*.[ch]' \) \( -exec grep -q '\$PostgreSQL' {} \; -o -print \) | while read file ; do head -n 1 < $file | grep -q '^/\*' && echo $file; done | xargs -l sed -i -e '1s/^\// /' -e '1i/*\n * $PostgreSQL:$ \n *' find . \( \( -name 'libstemmer' -o -name 'expected' -o -name 'ppport.h' \) -prune \) -o \( -name '*.[ch]' \) \( -exec grep -q '\$PostgreSQL' {} \; -o -print \) | xargs -l sed -i -e '1i/*\n * $PostgreSQL:$ \n */' | ||
* | pgindent run. | Bruce Momjian | 2003-08-04 |
| | |||
* | Changes to the parser to accept new datatypes. | Michael Meskes | 2003-03-21 |