Re: [COMMITTERS] 'pgsql/src/backend/parser parse.h gram.c' - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [COMMITTERS] 'pgsql/src/backend/parser parse.h gram.c'
Date
Msg-id Pine.BSF.4.05.9903022314480.59717-100000@thelab.hub.org
Whole thread Raw
In response to Re: [COMMITTERS] 'pgsql/src/backend/parser parse.h gram.c'  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
Responses Re: [COMMITTERS] 'pgsql/src/backend/parser parse.h gram.c'
List pgsql-hackers
On Wed, 3 Mar 1999, Thomas G. Lockhart wrote:

> > Modified Files:
> >         parse.h gram.c
> > Log Message:
> > Someone forgot to commit gram.c and parse.h after his latest
> > set of updates to gram.y.
> 
> I didn't forget! istm that we risk cvs bloat by checking in derived
> files like gram.c, when there are probably minor differences in how each
> system generates them. So I don't usually check in those files when we
> are deep in the middle of hacker development. Of course, that could be
> the wrong thing to (not) do...

Would have to agree here...developers *should* have the tools on their
systems required to generate this...these should only be
generated/committed as part of our pre-release checklist...

I think there are slightly more important things to worry about during
development...no? :)

Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: RE: [HACKERS] copyObject() ? again
Next
From: "Billy G. Allie"
Date:
Subject: ...