Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nfp0e-00013m-Oq for pgsql-committers@arkaria.postgresql.org; Sat, 16 Apr 2022 20:27:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nfp0c-0000Qd-In for pgsql-committers@arkaria.postgresql.org; Sat, 16 Apr 2022 20:27:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nfp0c-0000Pb-BN for pgsql-committers@lists.postgresql.org; Sat, 16 Apr 2022 20:27:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nfp0X-0007hr-8H for pgsql-committers@lists.postgresql.org; Sat, 16 Apr 2022 20:27:03 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 23GKQvg02021249; Sat, 16 Apr 2022 16:26:57 -0400 From: Tom Lane To: Peter Eisentraut cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Fix some trailing whitespace in documentation files In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Sat, 16 Apr 2022 07:05:39 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2021247.1650140817.1@sss.pgh.pa.us> Date: Sat, 16 Apr 2022 16:26:57 -0400 Message-ID: <2021248.1650140817@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut writes: > Fix some trailing whitespace in documentation files Hmm ... by my count there are still 245 lines with trailing spaces in the *.sgml files. (Most but not all are from copied-n-pasted psql output.) I'm not quite sure what's the point of retail fixes. I could get behind removing *all* these occurrences, and then adjusting .gitattributes so that git bleats about introducing new ones. Other folks might find that a little too obsessive-compulsive, though. regards, tom lane