Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fnank-00044Y-Ab for pgsql-docs@arkaria.postgresql.org; Thu, 09 Aug 2018 02:35:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fnanf-000169-Us for pgsql-docs@arkaria.postgresql.org; Thu, 09 Aug 2018 02:35:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fnanf-000162-Pe for pgsql-docs@lists.postgresql.org; Thu, 09 Aug 2018 02:35:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fnanX-0001Ix-Rh for pgsql-docs@lists.postgresql.org; Thu, 09 Aug 2018 02:35:42 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w792ZVa5027419; Wed, 8 Aug 2018 22:35:31 -0400 From: Tom Lane To: Bruce Momjian cc: Chris Travers , pgsql-docs@lists.postgresql.org Subject: Re: Release note trimming: another modest proposal In-reply-to: <20180809012707.GA9533@momjian.us> References: <19252.1533509841@sss.pgh.pa.us> <20180809012707.GA9533@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Wed, 08 Aug 2018 21:27:07 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <27417.1533782131.1@sss.pgh.pa.us> Date: Wed, 08 Aug 2018 22:35:31 -0400 Message-ID: <27418.1533782131@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Bruce Momjian writes: > Works for me, though, is there no interest in keeping the SGML files in > the git tree and just not building them as docs? Yeah, I thought about that alternative, but I'm not sure I see the percentage. It'd bloat the tarballs compared to removing them, and for what? Another point that's bothered me a bit is that we're failing to keep the historical notes historical. Every so often, somebody decides they need to run around and fix misspellings or whatever, and they do it to the old notes as well as stuff that's current. To me that goes against every principle of archiving. Taking old notes files out of the tree once we've stopped updating them would at least put a limit on how long they're exposed to historical revisionism. regards, tom lane