From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
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:43:08 |
Message-ID: | 442914.1752435788@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)justatheory(dot)com> writes:
> On Jul 13, 2025, at 15:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Alternatively, does git have any kind of metadata that isn't
>> a tag but acts sort of like one?
> Notes?
> https://git-scm.com/docs/git-notes
Hmm, maybe. I recall discussion about starting to use notes
to amend commit messages, and I'm not sure if this usage would
conflict with that. At the very least we'd need to write a
specification for what a note that triggers ABI-check behavior
looks like.
I'm still liking the in-tree-file idea better. For one thing,
it's not clear how expensive it'd be to search the git metadata
for this other stuff.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2025-07-13 19:47:18 | Re: ABI Compliance Checker GSoC Project |
Previous Message | Soumyadeep Chakraborty | 2025-07-13 19:28:11 | Re: Improve CRC32C performance on SSE4.2 |