From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Sigh ... |
Date: | 2008-05-03 19:20:30 |
Message-ID: | 481CBAFE.6030402@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Peter Eisentraut wrote:
>>> Btw., it is quite easily possible to use the autom4te tracing facility to
>>> parse the configure.ac file, in case you are interested in generating some of
>>> the Windows build code automatically.
>
>> Yeah, maybe. Let's fix the issue pg_config.h.win32 that Tom raised first.
>
> +1 for both. We really need to eliminate as much redundancy as we can
> between the two build systems, because it'll keep biting us until we do.
+1 from here as well, if that wasn' obvious :-)
(will get back to the actual issues at hand when I get back in a more
connected mode in a couple of days, unless they are already solved by then)
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | User Jbcooley | 2008-05-03 20:32:43 | npgsql - Npgsql: Allow IOException in listen thread to be handled by |
Previous Message | User H-saito | 2008-05-03 18:52:06 | psqlodbc - psqlodbc: Adjustment of a library. |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2008-05-03 23:35:37 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
Previous Message | Joshua D. Drake | 2008-05-03 17:31:01 | Re: statement timeout vs dump/restore |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-05-03 19:44:56 | Re: Exposing keywords to clients |
Previous Message | Andreas 'ads' Scherbaum | 2008-05-03 19:12:51 | Re: create or replace language |