| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian - CVS <momjian(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql (configure) |
| Date: | 2000-10-26 21:46:09 |
| Message-ID: | 22546.972596769@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> My server login checks to see if cvs update grabs configure, and if it
> does, it runs autoconf and commits the change.
If cvs update grabs configure, then someone already committed the
change.
Perhaps you meant configure.in. If so, I still doubt that this is
a good idea. If someone else is in process of committing
configure-related changes when you log in, the odds are that you
will screw them up, or at least confuse them mightily. configure
has more than one precursor file these days, so you might well commit
a broken copy.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-10-26 23:45:30 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
| Previous Message | Tom Lane | 2000-10-26 21:38:58 | pgsql/src/include/optimizer (planmain.h) |