From: Noah Misch <noah@leadboat.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jesse Zhang <sbjesse@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: run pgindent on a regular basis / scripted manner
Date: Wed, 12 Aug 2020 22:21:37 -0700
Message-ID: <20200813052137.GC1133236@rfd.leadboat.com> (raw)
In-Reply-To: <401351.1597295673@sss.pgh.pa.us>
References: <20200812223409.6di3y2qsnvynao7a@alap3.anarazel.de>
<CAGf+fX71Oa2vzg0xdj+vgrjmdVrm=kRLc7H3SEGtCHkGhoWDCg@mail.gmail.com>
<328084.1597276021@sss.pgh.pa.us>
<20200813035308.GA1137170@rfd.leadboat.com>
<397020.1597291716@sss.pgh.pa.us>
<20200813042655.GB1133236@rfd.leadboat.com>
<401351.1597295673@sss.pgh.pa.us>
On Thu, Aug 13, 2020 at 01:14:33AM -0400, Tom Lane wrote:
> Noah Misch <noah@leadboat.com> writes:
> > ... Another advantage of master-only is a guarantee against
> > disrupting time-critical patches. (It would be ugly to push back branches 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.
Atomicity is good. I just meant that you could issue something like "git push
origin $(cd .git/refs/heads && ls REL*)" to defer the complaint about master.
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: pgsql-hackers@postgresql.org
Cc: noah@leadboat.com, tgl@sss.pgh.pa.us, sbjesse@gmail.com, andres@anarazel.de
Subject: Re: run pgindent on a regular basis / scripted manner
In-Reply-To: <20200813052137.GC1133236@rfd.leadboat.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox