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 1m6HJu-0002TD-5i for pgsql-docs@arkaria.postgresql.org; Wed, 21 Jul 2021 18:51:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m6HJt-00063m-4y for pgsql-docs@arkaria.postgresql.org; Wed, 21 Jul 2021 18:51:49 +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 1m6HJs-00063e-VE for pgsql-docs@lists.postgresql.org; Wed, 21 Jul 2021 18:51:48 +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 1m6HJq-0003qq-L0; Wed, 21 Jul 2021 18:51:48 +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 16LIpcVM716629; Wed, 21 Jul 2021 14:51:38 -0400 From: Tom Lane To: Alvaro Herrera cc: Peter Eisentraut , "Jonathan S. Katz" , "Daniel Westermann (DWE)" , "pgsql-docs@lists.postgresql.org" Subject: Re: Link t the souce code In-reply-to: <202107211824.xki5acvkbiv2@alvherre.pgsql> References: <202107211824.xki5acvkbiv2@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Wed, 21 Jul 2021 14:24:42 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <716627.1626893498.1@sss.pgh.pa.us> Date: Wed, 21 Jul 2021 14:51:38 -0400 Message-ID: <716628.1626893498@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alvaro Herrera writes: > On 2021-Jul-21, Tom Lane wrote: >> I'm having qualms about recommending this in this particular spot, >> rather than back in Appendix I. Seems like the wrong audience is >> going to be reading this chapter. > Well, we can remove that first paragraph from there and just refer the > reader to the appendix ... something like this, perhaps. +1, though I think you're short a or so. > The appendix already has instructions on cloning the repo. It doesn't > say anything about branches though, but I'm not sure we want our docs to > become a tutorial on Git. We already link to git-scm.com though that's > not great; it doesn't explain our branch structure for example. We > could do better. Agreed that we're not here to teach people how to use git. But it'd be worth explaining our branch naming conventions in that appendix. It'd be sufficient I guess to mention "master" and "REL_n_STABLE"; by the time v15 sees the light of day, all the pre-v10 branches will be EOL. (Maybe also explain the REL_m_n release tags?) regards, tom lane