| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Enable script to generate preproc.y in build process. |
| Date: | 2008-11-14 19:42:57 |
| Message-ID: | 19957.1226691777@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> On Fri, Nov 14, 2008 at 12:13:30PM -0500, Tom Lane wrote:
>> Where's the "cvs remove preproc.y" ?
> Waiting for me to get online again. I didn't want to make that last change
> while going offline immediately afterwards. I prefer to be able to keep an eye
> on the buildfarm for the first few builds after changes to the build system.
I didn't think we were getting any real testing with the preproc.y file
still being there --- it would depend on chance file update times
whether the preproc.y file got rebuilt or not.
In any case, one can always roll back a CVS change ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-11-14 19:47:50 | pgsql: In CREATE AGGREGATE, allow the transition datatype to be |
| Previous Message | Michael Meskes | 2008-11-14 19:26:59 | Re: pgsql: Enable script to generate preproc.y in build process. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2008-11-14 20:25:51 | Re: pgsql: Enable script to generate preproc.y in build process. |
| Previous Message | Michael Meskes | 2008-11-14 19:26:59 | Re: pgsql: Enable script to generate preproc.y in build process. |