| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Antonin Houska <ah(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_config_h.in not up-to-date |
| Date: | 2021-02-19 07:13:24 |
| Message-ID: | YC9lFCSScmY5k7Dl@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 19, 2021 at 01:42:38AM -0500, Tom Lane wrote:
> Antonin Houska <ah(at)cybertec(dot)at> writes:
>> When I run "autoreconf" on the master branch, git generates the diff
>> below. Shouldn't it just be applied? I suppose someone changed configure.ac
>> and forgot to update the generated file.
>
> Yeah, looks like fe61df7f8 is at fault. Michael?
Indeed, thanks. It looks like a "git add" that was fat-fingered. I
would like to make things more consistent with the attached.
Thoughts?
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| openssl-autoconf.patch | text/x-diff | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-02-19 07:14:17 | Re: Problem with accessing TOAST data in stored procedures |
| Previous Message | Konstantin Knizhnik | 2021-02-19 06:51:23 | Re: Problem with accessing TOAST data in stored procedures |