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

From: geek+(at)cmu(dot)edu
To: Postgres Hackers List <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser parse.h gram.c'
Date: 1999-03-03 13:43:03
Message-ID: emacs-smtp-22924-14045-15463-819491@export.andrew.cmu.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Then <lockhart(at)alumni(dot)caltech(dot)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(at)andrew(dot)cmu(dot)edu for my public key. |
=====================================================================

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vince Vielhaber 1999-03-03 13:44:59 pg_dumpall and restoring
Previous Message The Hermit Hacker 1999-03-03 13:38:58 Re: [HACKERS] int 8 on FreeBSD