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 1k65Zc-00084T-Vm for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Aug 2020 05:14:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k65Zb-0004NA-VH for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Aug 2020 05:14:43 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k65Zb-0004N3-ON for pgsql-hackers@lists.postgresql.org; Thu, 13 Aug 2020 05:14:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k65ZV-0002VP-Gg for pgsql-hackers@postgresql.org; Thu, 13 Aug 2020 05:14:42 +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 07D5EXCg401352; Thu, 13 Aug 2020 01:14:33 -0400 From: Tom Lane To: Noah Misch cc: Jesse Zhang , Andres Freund , PostgreSQL-development Subject: Re: run pgindent on a regular basis / scripted manner In-reply-to: <20200813042655.GB1133236@rfd.leadboat.com> References: <20200812223409.6di3y2qsnvynao7a@alap3.anarazel.de> <328084.1597276021@sss.pgh.pa.us> <20200813035308.GA1137170@rfd.leadboat.com> <397020.1597291716@sss.pgh.pa.us> <20200813042655.GB1133236@rfd.leadboat.com> Comments: In-reply-to Noah Misch message dated "Wed, 12 Aug 2020 21:26:55 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <401350.1597295673.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Aug 2020 01:14:33 -0400 Message-ID: <401351.1597295673@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Noah Misch writes: > ... Another advantage of master-only is a guarantee against > disrupting time-critical patches. (It would be ugly to push back branch= es and > sort out the master push later, but it doesn't obstruct the mission.) Hm, doesn't it? I had the idea that "git push" is atomic --- either all the per-branch commits succeed, or they all fail. I might be wrong. regards, tom lane