Re: [HACKERS] [PATCH] Remove trailing whitespaces from documentation - Mailing list pgsql-hackers

From Vladimir Rusinov
Subject Re: [HACKERS] [PATCH] Remove trailing whitespaces from documentation
Date
Msg-id CAE1wr-z=9m8MkpqYbitM17L=Py0WVwcW97bKeCVR80sVuCm+7w@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [PATCH] Remove trailing whitespaces from documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Dec 14, 2016 at 4:50 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Vladimir Rusinov <vrusinov@google.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

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Hash Indexes
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] [PATCH] Remove trailing whitespaces from documentation