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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1rfNYL-00HIPM-R3
	for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Feb 2024 17:17:10 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1rfNYK-00D0U2-5K
	for pgsql-hackers@arkaria.postgresql.org; Wed, 28 Feb 2024 17:17:08 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rfNYJ-00D0Tu-Sn
	for pgsql-hackers@lists.postgresql.org; Wed, 28 Feb 2024 17:17:08 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rfNYG-001r0S-Lq
	for pgsql-hackers@postgresql.org; Wed, 28 Feb 2024 17:17:07 +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 41SHH4022322054;
	Wed, 28 Feb 2024 12:17:04 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
cc: Daniel Gustafsson <daniel@yesql.se>,
        Andrew Atkinson <andyatkinson@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@postgresql.org>, samay@tembo.io
Subject: Re: An improved README experience for PostgreSQL
In-reply-to: <20240228170237.GB2435539@nathanxps13>
References: <CAG6XLEmGE95DdKqjk+Dd9vC8mfN7BnV2WFgYk_9ovW6ikN0YSg@mail.gmail.com> <20240226183018.GA2109010@nathanxps13> <1967819.1708979436@sss.pgh.pa.us> <DAB16F23-BE05-44E3-80DB-8D60961B8906@yesql.se> <20240228170237.GB2435539@nathanxps13>
Comments: In-reply-to Nathan Bossart <nathandbossart@gmail.com>
	message dated "Wed, 28 Feb 2024 11:02:37 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2322052.1709140624.1@sss.pgh.pa.us>
Date: Wed, 28 Feb 2024 12:17:04 -0500
Message-ID: <2322053.1709140624@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/2322053.1709140624%40sss.pgh.pa.us>
Precedence: bulk

Nathan Bossart <nathandbossart@gmail.com> writes:
> Sorry, my suggestion wasn't meant to imply that I have any strong concerns
> about maintaining two README files.  If we can automate generating one or
> the other, that'd be great, but I don't see that as a prerequisite to
> adding a Markdown version.

Agreed, and I'd go so far as to say that adding automation now
would be investing work that might well go to waste.  When and
if we get annoyed by the manual labor involved in maintaining
two copies, it'd be time to put work into automating it.

			regards, tom lane