| 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>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql-server/. HISTORY |
| Date: | 2002-09-09 17:27:18 |
| Message-ID: | 12128.1031592438@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:
> Peter Eisentraut wrote:
> You should be making these changes in release.sgml, from where HISTORY
> will be generated.
>
> It is too hard to edit two files. Until we get near final it is just
> easier to do the one.
>>
>> Yes, "the one" is release.sgml, and the other is generated automatically.
>> No need to edit two files.
> Unless it gets auto-generated every time I make a commit to /HISTORY, I
> am not interested.
That argument seems about on a par with wanting to hand-edit the
configure script because we don't automatically run autoconf when you
check in configure.in. If you want an automatic update procedure,
surely it would be easy to cause that to happen.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut - PostgreSQL | 2002-09-09 18:35:05 | pgsql-server/src/bin/pg_config Makefile |
| Previous Message | Peter Eisentraut | 2002-09-09 17:17:58 | Re: pgsql-server/. configure configure.in |