Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cqVQ8-00073X-PM for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Mar 2017 01:50:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cqVQ8-0005rR-C0 for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Mar 2017 01:50:40 +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 1cqVQ7-0005nB-7Z; Wed, 22 Mar 2017 01:50:39 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cqVQ4-0003Zy-B1; Wed, 22 Mar 2017 01:50:37 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6FD7320A76; Tue, 21 Mar 2017 21:50:35 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 21 Mar 2017 21:50:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=w9fu+KlKPWj8GUlmdZKY3gl2SqE0+jEhnvrDBdz9GpA=; b=pjfHEmwJ k3byBOrKdkBq0nbkHaULjlOnYQjUvML0q5FY10YaCVprFMcapcfHxE9heybl6uo4 SR16azT0F63loCOrEw3f4XxvD399xWqC6EjeEjUrC5+NZafpkgW7b4dRM45f8aCP olD8/wLCiNraBzNqnM1eOmHl6CW50warf4H9PKvAlOMgPv28Zzn9362YNG73Rjou A9A2iS+wfRPXLUEWUmas3dhqKg6SiUwFFTzo3j0NGIojF8zowHcXKQUti/FhB41s iR3zOQbyVK9jQgR3ZN39w+UVC81OMM1E7ta9+4+leWgqqIClpCLi0Mfjt9zGy+Zo o/bwLq8NXDElrw== X-ME-Sender: X-Sasl-enc: j7zoYgOH1TWh00ChHXdF914ZvVgT90369LyNTQ0HiE23 1490147435 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 2C8997E334; Tue, 21 Mar 2017 21:50:35 -0400 (EDT) Subject: Re: Questionable tag usage To: Tom Lane , Tatsuo Ishii References: <20170105.092557.1822243556008160851.t-ishii@sraoss.co.jp> <25963.1483591811@sss.pgh.pa.us> Cc: pgsql-docs@postgresql.org, pgsql-hackers@postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Tue, 21 Mar 2017 21:50:42 -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 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 1/11/17 11:55, Peter Eisentraut wrote: > On 1/4/17 11:50 PM, Tom Lane wrote: >> Anyway, bottom line is I'm not terribly excited about fixing just this >> one place. I think we need to decide whether we like the new more-verbose >> output for links. If we don't, we need to fix the markup rules to not do >> that. If we do, there are a lot of places that need adjustment to be less >> duplicative, and we should try to be somewhat systematic about fixing >> them. > > We can turn off the new link appearance and change it back to the old > one. We had previously speculated that this change might be awkward in > some cases, but without any concrete cases. If we have concrete cases, > we can change it. This question is still open. Do we want to keep the new linking style Section 1.2.3, "Title", or revert back to the old style just Section 1.2.3? It's a simple toggle setting. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers