Re: run pgindent on a regular basis / scripted manner - Mailing list pgsql-hackers

From Jesse Zhang
Subject Re: run pgindent on a regular basis / scripted manner
Date
Msg-id CAGf+fX4WGztdE19t_iabAd=tBa==175WQ4QDi08Cr6j7h4ihXw@mail.gmail.com
Whole thread Raw
In response to Re: run pgindent on a regular basis / scripted manner  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Aug 12, 2020 at 10:14 PM 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.

As of Git 2.28, atomic pushes are not turned on by default. That means
"git push my-remote foo bar" _can_ result in partial success. I'm that
paranoid who does "git push --atomic my-remote foo bar fizz".

Cheers,
Jesse



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: security_context_t marked as deprecated in libselinux 3.1
Next
From: Tom Lane
Date:
Subject: Re: security_context_t marked as deprecated in libselinux 3.1