Re: [HACKERS] src/interfaces/libpq shipping nmake-related Makefiles
| От | Magnus Hagander |
|---|---|
| Тема | Re: [HACKERS] src/interfaces/libpq shipping nmake-related Makefiles |
| Дата | |
| Msg-id | CABUevEy1r94m2_AaUrXZC87BTxtEQL_FsMQo=J4xpczbdrnKLQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] src/interfaces/libpq shipping nmake-related Makefiles (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>) |
| Ответы |
Re: [HACKERS] src/interfaces/libpq shipping nmake-related Makefiles
|
| Список | pgsql-hackers |
On Fri, Apr 7, 2017 at 4:03 PM, Andrew Dunstan <andrew.dunstan@2ndquadrant.com> wrote:
On 04/07/2017 09:58 AM, Tom Lane wrote:
>> This seems be the same as the 2nd error that was reported back in 2013:
>> https://www.postgresql.org/message-id/CAJ2% 3DPVQcW8UGNnSy%3DOw% 3DvUK2zpjowTkzUS1B864REa7LOT14 0Q%40mail.gmail.com.
> Well, if it's been broken since (at least) 2013, and we've had only one
> complaint, then I'd say there are too few potential users to justify
> the maintenance burden.
>
>
I agree.
Are these votes for getting rid of both win32.mak and bcc32.mak?
If so, count me in for the same :) Want me to do the honors, as it's my fault they're in there in the first place?
В списке pgsql-hackers по дате отправления: