Thread

1. Re: [COMMITTERS] 'pgsql/src/backend/parser parse.h gram.c'

   Thomas Lockhart <lockhart@alumni.caltech.edu> — 1999-03-03T02:45:11Z

   > 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...
   
                       - Tom
   
   

2. Re: [COMMITTERS] 'pgsql/src/backend/parser parse.h gram.c'

   Marc G. Fournier <scrappy@hub.org> — 1999-03-03T03:15:50Z

   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 
   
   
   

3. Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser parse.h gram.c'

   Brian E Gallew <geek+@cmu.edu> — 1999-03-03T13:43:03Z

   Then <lockhart@alumni.caltech.edu> spoke up and said:
   > > 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...
   
   You *never* want to check in derived files when using CVS.  Instead,
   create checkout rules (see the cvs docs) to automatically create those
   files upon checkin/checkout, whichever is more appropriate.
   
   -- 
   =====================================================================
   | JAVA must have been developed in the wilds of West Virginia.      |
   | After all, why else would it support only single inheritance??    |
   =====================================================================
   | Finger geek@andrew.cmu.edu for my public key.                     |
   =====================================================================