From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Vladimir Rusinov <vrusinov(at)google(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Remove trailing whitespaces from documentation |
Date: | 2016-12-14 23:31:38 |
Message-ID: | 012567a6-12e3-01dd-5207-aecbf8b27e9e@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/14/16 5:12 PM, Stephen Frost wrote:
> For my 2c, at least, because we're going to be constantly fighting with
> the trailing whitespace in those examples. If you forget to s/</</g,
> the docs aren't going to build and it's going to be extremely obvious
> that you need to do something. Not that I'm actually happy about that-
> I'd much rather tell the doc engine "copy this verbatim until you see a
> </closeverbatim> tag" or whatever, and not have to go hack up psql
> output at all,
This already exists: git grep -w CDATA
> That said, if we can make git complain about trailing whitespace in the
> docs but not mind it in the regression test output, then at least most
> will hopefully realize that they need to go through and strip out the
> trailing whitespace before committing.
That would be easy to do.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Rusinov | 2016-12-14 23:37:27 | Re: Make pg_basebackup -x stream the default |
Previous Message | Vladimir Rusinov | 2016-12-14 23:10:00 | Re: [PATCH] Remove trailing whitespaces from documentation |