Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d5am0-0002sT-HK for pgsql-docs@arkaria.postgresql.org; Tue, 02 May 2017 16:35:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d5alz-0002XL-VC for pgsql-docs@arkaria.postgresql.org; Tue, 02 May 2017 16:35:36 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d5alb-00016T-24 for pgsql-docs@postgresql.org; Tue, 02 May 2017 16:35:11 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d5alX-00089d-Hk for pgsql-docs@postgresql.org; Tue, 02 May 2017 16:35:09 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id C3F2720800 for ; Tue, 2 May 2017 12:35:06 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 02 May 2017 12:35:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=2SDhXYqoBwDhvD1J7ySXPjtJ8anPlUl6sALQkF+4D vw=; b=Cf+vozWj7QsOLFeu3BFnnb2vV+/erLe6Pead1/LzuaU9TL/b8Xw449ZhF JemBLFQyhMC1tZYTV9kFON9646u7yV+Eo9lV0FTNHEngzg1cbAGgemHEU0qTw1H4 I7mWcHTChXnPYztkCkLOj16V3pdFN1Csc5k8Klvsn78YZiFZEdAE16EqrR1eXGpi 2PzZLF+85yeU/xkWDeihfbgmuy67L3Kj+oYXEwvQYLnOmcfgvJzVbnenpdaL/J7S TdbQOmbl7jok3KXm5/AEHTJilLT3fhoO8t3GIDwtWP3LWx9mrqrgXD4tZT8aLTRs QeTFwPuJwC2Bns+dZp8JxPqmUjdkQ== X-ME-Sender: X-Sasl-enc: UR9k8MNlMGrikcGHe7MM5zoAlXBHiG/Q10ge+ZZh+Ck+ 1493742906 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 8D2E224140 for ; Tue, 2 May 2017 12:35:06 -0400 (EDT) To: pgsql-docs@postgresql.org From: Peter Eisentraut Subject: release date formatting Organization: 2ndQuadrant Message-ID: <2b8a2552-fffa-f7c8-97c5-14db47a87731@2ndquadrant.com> Date: Tue, 2 May 2017 12:35:06 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------E25A1C57C0AF358FDD0AFD38" X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org This is a multi-part message in MIME format. --------------E25A1C57C0AF358FDD0AFD38 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit It has been pointed out a while ago that the "release date" formatting in the release notes is too flamboyant, more so under the new stylesheets. Here is a patch to make the formatting a bit more subdued. (Obviously, this needs to be expanded to older release notes as well.) -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services --------------E25A1C57C0AF358FDD0AFD38 Content-Type: invalid/octet-stream; name="0001-doc-Refine-release-date-formatting.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0001-doc-Refine-release-date-formatting.patch"