Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qkkPh-00GApN-GN for pgsql-docs@arkaria.postgresql.org; Mon, 25 Sep 2023 12:10:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qkkPf-000nmY-Pm for pgsql-docs@arkaria.postgresql.org; Mon, 25 Sep 2023 12:10:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qkkPf-000nmQ-Hc for pgsql-docs@lists.postgresql.org; Mon, 25 Sep 2023 12:10:07 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qkkPY-007Tve-5D for pgsql-docs@lists.postgresql.org; Mon, 25 Sep 2023 12:10:06 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id D34952FA64AF for ; Mon, 25 Sep 2023 14:09:58 +0200 (CEST) Received: from s934.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id C4B382E28C75 for ; Mon, 25 Sep 2023 14:09:58 +0200 (CEST) Received: from s474.loopia.se (unknown [172.22.191.6]) by s934.loopia.se (Postfix) with ESMTP id C38AD7CEA73 for ; Mon, 25 Sep 2023 14:09:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=disabled Received: from s979.loopia.se ([172.22.191.6]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id 1OoTiaGkLj9U for ; Mon, 25 Sep 2023 14:09:58 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s979.loopia.se (Postfix) with ESMTPSA id 5BDC510BC46B for ; Mon, 25 Sep 2023 14:09:58 +0200 (CEST) From: Daniel Gustafsson Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Hyperlinks for source file references Message-Id: <7C6E4AF2-62BA-49AB-8EC6-FA27136A8B88@yesql.se> Date: Mon, 25 Sep 2023 14:09:58 +0200 To: pgsql-docs@lists.postgresql.org X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Commit b73c3a11963 introduced xyz hyperlinks for files in the postgres source tree by linking to the = gitweb interface at git.postgresql.org. This, IMO, makes the content referred = to more accessible, and is especially interesting for README files. The links = in question can be found here: https://www.postgresql.org/docs/devel/tableam.html Right now we have ~85 references to source files using in = the docs, should we convert them to hyperlinks like the ones in the Table AM = docs? I would be happy to make a patch that implements this, but I wanted to = check here before making the effort to make sure it's not immediately nayed. This does of course present a question for the backbranches, pointing to = the HEAD version in the docs for a previous major release isn't entirely = accurate. On the other hand, we already do that today in the above tableam page so = if we don't like that we might as well sort out now what to do about that. -- Daniel Gustafsson