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 1ngo6l-0006nJ-FX for pgsql-committers@arkaria.postgresql.org; Tue, 19 Apr 2022 13:41:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ngo6k-00019t-9C for pgsql-committers@arkaria.postgresql.org; Tue, 19 Apr 2022 13:41:30 +0000 Received: from makus.postgresql.org ([72.32.157.229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ngo6k-00018s-1A for pgsql-committers@lists.postgresql.org; Tue, 19 Apr 2022 13:41:30 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ngo4a-0005ch-1z for pgsql-committers@lists.postgresql.org; Tue, 19 Apr 2022 13:39:18 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 152855C00DF; Tue, 19 Apr 2022 09:39:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 19 Apr 2022 09:39:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1650375555; x=1650461955; bh=gMEcUHAlzhXWk EVDrJNh7oxd+tkx5M483j/ucURSIS4=; b=m+CSr0xu8LvpxfTtuIcFx9n994G3j 4fQljqvu/Wafic/ZXyzidI0RxegeXQdXnTj+x0KWCYYpzjfAm+kdA5I1Alwd0SO9 bHgSDBxiA2iMoB2M9rAaSDs5lmQeB2euQ4P3ebL49/jSxEKz6Qgsv2MoXCsZFnnG e+s6kFwVGT1bCr+//SBQ9JaDeZmuqwXswxzBS/bhZkno2YnJtJPaZUGlUnXqHnNi JVDUZZo4BF7MtX8i/PYrf/5Hu6kpuEH72aglQbCdwguv8Y1R7HGnM/IIW7hw6DD4 XWH5qtA22eygsEJvNi1n/m722LX2j4EEa9ZViqBUmnPZJlajABCv961ng== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrvddtfedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtje ertddtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr rdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhmqeenucggtffrrg htthgvrhhnpeefjeegheetuefhveevudelueeftdejteeiffetvdduhfdtieefgfeutedt veeggfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 19 Apr 2022 09:39:14 -0400 (EDT) Message-ID: <90abc132-ab5a-cbef-b330-8d58c24e4c6c@enterprisedb.com> Date: Tue, 19 Apr 2022 15:39:12 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: pgsql: Fix some trailing whitespace in documentation files Content-Language: en-US To: Tom Lane Cc: pgsql-committers@lists.postgresql.org References: <2021248.1650140817@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <2021248.1650140817@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 16.04.22 22:26, Tom Lane wrote: > 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. If someone wants to set that up, I'm not opposed. In the meantime, I'm content to clean up stray whitespace once in a while. I don't want to not do that, because otherwise too much junk will accumulate.