| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com> |
| Subject: | Re: Commitfest app release on Feb 17 with many improvements |
| Date: | 2025-03-06 23:48:36 |
| Message-ID: | CAGECzQQ+ZxgJaCb3w+hKbcZfwZwZ=-_0G8_06xZA5AF3c0mn8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 6 Mar 2025 at 18:39, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
>
> On Thu, 6 Mar 2025 at 18:10, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Please see if you can make it use patch(1). IME git is too
> > stiff-necked about slightly stale patches no matter which
> > subcommand you use.
>
> It was using patch(1) in the past for that reason, but with --3way I
> was able to get "git apply" to apply patches that patch(1) was unable
> to apply. Also with the git command you get much more useful conflict
> output.
Okay, I went for the approach of just trying everything until one
works. Starting with "git am", then patch(1), and as a final attempt
"git apply". Patch 5272 applies correctly now. I've removed any
backoff caused by repeated failures for all existing patches, so all
should be retried in the next ~48 hours.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2025-03-07 00:03:02 | Re: what's going on with lapwing? |
| Previous Message | Jacob Champion | 2025-03-06 23:39:44 | Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible |