From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
Subject: | Re: ABI Compliance Checker GSoC Project |
Date: | 2025-07-13 19:10:57 |
Message-ID: | F3F86A0B-B56B-4F6D-8716-1E88F9742129@justatheory.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 13, 2025, at 15:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> On reflection, assuming that this is being run by one or more
> buildfarm animals, there are not likely to be so many commits
> between runs that it'll be hard to assign blame after a breakage.
> So I'm not convinced that we need to build the logic you describe.
Fair. Better to start simple and add something like this later if it’s a PITA without it.
> Alternatively, does git have any kind of metadata that isn't
> a tag but acts sort of like one? The fact that you cannot
> move or remove a tag once pushed could come back to bite us
> if we start using them for this purpose.
Notes?
https://git-scm.com/docs/git-notes
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Melanie Plageman | 2025-07-13 19:15:22 | Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) |
Previous Message | Tom Lane | 2025-07-13 19:02:48 | Re: ABI Compliance Checker GSoC Project |