From: | Vladimir Rusinov <vrusinov(at)google(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Remove trailing whitespaces from documentation |
Date: | 2016-12-14 18:04:01 |
Message-ID: | CAE1wr-zpzVQ5tNbT5BJ7wO-MHjhUUjSL3MfU-A6aC0Q8U6aGFA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 14, 2016 at 5:41 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > They are considered bad practice in many style guides and many editors
> > configured to stip them on every save.
> >
> > Such editors will produce spurious diffs when editing the documentation.
> >
> > Therefore, I propose this patch.
>
> As mentioned down-thread, most of this is from psql output and I don't
> know that we actually want to get rid of that whitespace. Ideally, we
> could indicate that trailing whitespace should be preserved when
> printing examples, either with the SGML or the XML format.
>
> The (relativly few) ones I include below do look like cases we should
> probably fix and back-patch (to simplify later back-patching efforts).
> Most of these only go back to 9.6 (parallel.sgml) anyway.
I'm not sure if it makes sense to merge just these, as it will not help
people with whitespace-eating editors.
--
Vladimir Rusinov
Storage SRE, Google Ireland
Google Ireland Ltd.,Gordon House, Barrow Street, Dublin 4, Ireland
Registered in Dublin, Ireland
Registration Number: 368047
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2016-12-14 18:07:11 | Re: [PATCH] Remove trailing whitespaces from documentation |
Previous Message | Stephen Frost | 2016-12-14 17:41:52 | Re: [PATCH] Remove trailing whitespaces from documentation |