| From: | Jesse Zhang <sbjesse(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: run pgindent on a regular basis / scripted manner |
| Date: | 2020-08-13 05:24:41 |
| Message-ID: | CAGf+fX4WGztdE19t_iabAd=tBa==175WQ4QDi08Cr6j7h4ihXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 12, 2020 at 10:14 PM Tom Lane wrote:
>
> Noah Misch <noah(at)leadboat(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-13 05:29:35 | Re: security_context_t marked as deprecated in libselinux 3.1 |
| Previous Message | Michael Paquier | 2020-08-13 05:22:41 | Re: security_context_t marked as deprecated in libselinux 3.1 |