Re: [PATCH] Remove trailing whitespaces from documentation

From: Vladimir Rusinov <vrusinov(at)google(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Remove trailing whitespaces from documentation
Date: 2016-12-14 17:25:49
Message-ID: CAE1wr-z=9m8MkpqYbitM17L=Py0WVwcW97bKeCVR80sVuCm+7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 14, 2016 at 4:50 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Vladimir Rusinov <vrusinov(at)google(dot)com> writes:
> > Therefore, I propose this patch.
>
> Right now is a really bad time to do that; what it will mostly accomplish
> is to break back-patching of doc fixes for little benefit.
>

ack. As I said, it's a proposal and I'm not too attached to it.
Glad it sparked some discussions though.

That said, I don't fully buy this argument: diff is very simple. Merge
conflicts during backporting will be trivial to fix, although a bit more
annoying.

> There is work afoot to convert the documentation to xml. If that
> succeeds, it'd make sense to strip trailing spaces (and start enforcing
> that in .gitattributes) when we do that, since it'll be a back-patch
> breakpoint anyway. But right now the PITA factor outweighs the benefit.
>

What is the ETA for this work to be complete (or fail and be abandoned)?

--
Vladimir Rusinov
Storage SRE, Google Ireland

Google Ireland Ltd.,Gordon House, Barrow Street, Dublin 4, Ireland
Registered in Dublin, Ireland
Registration Number: 368047

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2016-12-14 17:30:28 Re: [PATCH] Remove trailing whitespaces from documentation
Previous Message Robert Haas 2016-12-14 17:17:47 Re: Hash Indexes