From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Chris Browne <cbbrowne(at)acm(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: [COMMITTERS] pgsql: Second try committing the path changes. |
Date: | 2006-08-31 17:50:50 |
Message-ID: | 21827.1157046650@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Chris Browne <cbbrowne(at)acm(dot)org> writes:
> tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) writes:
>> No, because those derived files are not in CVS at all. What you
>> are describing sounds to me like a clock skew problem. Is your
>> machine's system clock showing the correct date?
> Odd, odd. NOT a clock problem. The .c files were sitting in my
> buildfarm's CVS repository for HEAD. And yes, indeed, the derived
> files shouldn't have been there at all. I'm not quite sure how they
> got there in the first place.
> At any rate, after comprehensively looking for yacc-derived files,
> that clears this problem, as well as regression failures with last
> night's commit of COPY (SELECT) TO, which is no bad thing.
I'll bet the way they got there is you did a build in the CVS repository
tree, and then cleaned up with "make distclean" not "make maintainer-clean".
The buildfarm script is supposed to complain about unexpected files in
the repository --- I wonder if it is fooled by the .cvsignore entries
for these files?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-08-31 18:09:37 | Re: [COMMITTERS] pgsql: Second try committing the path |
Previous Message | User Gsmet | 2006-08-31 17:35:03 | pgfouine - pgfouine: Prepared statements support round 2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-08-31 18:01:09 | Re: Prepared statements considered harmful |
Previous Message | Magnus Hagander | 2006-08-31 17:44:00 | Re: gBorg status? |