Re: Commitfest app release on Feb 17 with many improvements

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: Andreas Karlsson <andreas(at)proxel(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Commitfest app release on Feb 17 with many improvements
Date: 2025-03-07 16:42:35
Message-ID: 1024103.1741365755@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> writes:
> On Fri, 7 Mar 2025 at 11:26, Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
>> Out of curiosity: do you track which method works? I would expect
>> everything to be applied with either git am or patch which can be
>> applied with git apply making git apply technically unnecessary.

> I think we need all of them...
> - git apply is unable to apply the patch in 5272 on top of main
> - git am, works with that 5272, but cannot apply any patch not created
> by git format-patch (for instance 5522)
> - I've been unable to get patch(1) not to return a failure if the
> patch is already applied. So applying e.g. 5522 twice. git apply
> handles that fine.

Hm, don't you *want* a failure if the patch is already applied?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-03-07 16:46:53 Re: [PATCH] New predefined role pg_manage_extensions
Previous Message Andres Freund 2025-03-07 16:41:38 Re: strange valgrind reports about wrapper_handler on 64-bit arm