Re: renaming configure.in to configure.ac

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: renaming configure.in to configure.ac
Дата
Msg-id BE7F4FC9-F215-414F-B41F-3139A36F0464@anarazel.de
обсуждение исходный текст
Ответ на Re: renaming configure.in to configure.ac  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: renaming configure.in to configure.ac  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hi,

On July 16, 2020 8:24:15 AM PDT, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>Noah Misch <noah@leadboat.com> writes:
>> On Wed, Jul 15, 2020 at 09:45:54AM -0400, Tom Lane wrote:
>More ambitiously, we could just adopt 2.69b in HEAD and see what
>happens,
>planning to revert only if things break.  The cost to that is that
>committers who want to commit configure.ac changes would have to
>install
>2.69b.  But they'd be having to install 2.70 whenever we move to that,
>anyway, so I'm not sure that's a big cost.

I think it'd be a good plan to adopt the beta on master.

We already have parts of it backpacked, there have been things we couldn't easily do because of bugs in 2.69. There
aren'tthat many changes to configure it total, and particularly not in the back branches. So I think it'd be ok
overheadwise. 

Andres

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: renaming configure.in to configure.ac
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Volatile Functions in Parallel Plans