public inbox for [email protected]
help / color / mirror / Atom feedFrom: Nathan Bossart <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Why does pgindent's README say to download typedefs.list from the buildfarm?
Date: Mon, 22 Apr 2024 15:20:10 -0500
Message-ID: <20240422202010.GA420168@nathanxps13> (raw)
In-Reply-To: <[email protected]>
References: <20240422192218.GB367217@nathanxps13>
<[email protected]>
On Mon, Apr 22, 2024 at 04:08:08PM -0400, Tom Lane wrote:
> I think the actual plan now is that we'll sync the in-tree copy
> with the buildfarm's results (and then do a tree-wide pgindent)
> every so often, probably shortly before beta every year.
Okay. Is this just to resolve the delta between the manual updates and a
clean autogenerated copy every once in a while?
> The problem with the README is that it describes that process,
> rather than the now-typical workflow of incrementally keeping
> the tree indented. I don't think we want to remove the info
> about how to do the full-monty process, but you're right that
> the README needs to explain the incremental method as being
> the one most developers would usually use.
>
> Want to write some text?
Yup, I'll put something together.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
view thread (4+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Why does pgindent's README say to download typedefs.list from the buildfarm?
In-Reply-To: <20240422202010.GA420168@nathanxps13>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox