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 1rz09D-001TNh-NE for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Apr 2024 20:20:19 +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 1rz09C-00FVMU-9E for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Apr 2024 20:20:18 +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 1rz09B-00FVMK-Vr for pgsql-hackers@lists.postgresql.org; Mon, 22 Apr 2024 20:20:18 +0000 Received: from mail-il1-x12a.google.com ([2607:f8b0:4864:20::12a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rz099-002OlD-BM for pgsql-hackers@postgresql.org; Mon, 22 Apr 2024 20:20:17 +0000 Received: by mail-il1-x12a.google.com with SMTP id e9e14a558f8ab-36a38c13550so19849035ab.0 for ; Mon, 22 Apr 2024 13:20:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713817213; x=1714422013; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=AZClebpGv2wxRACfXycImU+TStcp4FXsVA5o7WPPZ4U=; b=VDzVoRq26TVmpEWu+ZNQPk0DmECltf9cGGsNTxz/SL98rzaQQpD/gR5Me1D3RiNGV3 R68T1wIgnxRd5VyBrxSjmX7R9MWyyNWcqMQNmv90OjZf6M2qjHFVRSbPmAJYM2vdu/rc xGOX/jkJTQR2fgV51A131SgesWLqXq1meKaXyb/b5162oGYSwaRSeqbD4nOPU335sM3S jsVLaSya2Uzfq+qFNtioYr43mGgB18BSLlVLW0psPwFWspKzELxER3Hf0rDLU+0mkXyr bajAM9ogBFE1/vaMNEXX9a8V9lRiKb8xVvf5jpTTMVPZc3EuQoACnJmle7G9wERdRNjq W9cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713817213; x=1714422013; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=AZClebpGv2wxRACfXycImU+TStcp4FXsVA5o7WPPZ4U=; b=kamkbUDjVy5mQkDDU2Sa6Mjj/GCWiQ9f1Of9YnKQFUiSTF+DwyRnoaUvy4NEbiCKGN ycMDkAmGQn9KwWvCzLs97Jbrm4Ux36g4DvOPjAUfpZYCY3/EEurTRlzKM8z28Ua+Haf6 /FluBKBwdweuN2JFO0qQANEO0+TuU9dYbnbW14okZZCS03sfcXL2VpisgTjcIlcK2XAb wamcFAUUkxLfBNvkVRxQsLC27qXjGnbiGKF5reDdngagrYqRRN0Plt13od2rXcyIPt0Q SyN5YxZtcRD9SvrUq0T5WwImL6c9bMPz/z4C3F1HxTHSXOd/zAkeg63LEp8wMNiplE9G VRZw== X-Gm-Message-State: AOJu0YzJOOsoa7gYwlved0NShKvA0B+/HazFEsCy5ByMNDbrhTPzUiE1 AcmuSEpFtn6rxwvYQ7Qq5yuIZrAgs9Cayoi4tsKq4R0fgHbKjoiYP7B+Iw== X-Google-Smtp-Source: AGHT+IEwe0N4RjkjEJP6re49GpsZGZHL+2YV3mqQrgHxuumwQeC51s8u7z6TT6yr9tq7/LfIj8yuIw== X-Received: by 2002:a05:6e02:16cb:b0:36a:2333:3665 with SMTP id 11-20020a056e0216cb00b0036a23333665mr15172269ilx.30.1713817212828; Mon, 22 Apr 2024 13:20:12 -0700 (PDT) Received: from nathanxps13 (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id o9-20020a056e02068900b0036b36beece8sm2292531ils.79.2024.04.22.13.20.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 Apr 2024 13:20:12 -0700 (PDT) Date: Mon, 22 Apr 2024 15:20:10 -0500 From: Nathan Bossart To: Tom Lane Cc: pgsql-hackers@postgresql.org Subject: Re: Why does pgindent's README say to download typedefs.list from the buildfarm? Message-ID: <20240422202010.GA420168@nathanxps13> References: <20240422192218.GB367217@nathanxps13> <3154983.1713816488@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3154983.1713816488@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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