pgsql-server/. HISTORY

Bruce Momjian - CVS writes:

Modified files:
. : HISTORY

Log message:
Reorder items.

You should be making these changes in release.sgml, from where HISTORY
will be generated.

--
Peter Eisentraut peter_e@gmx.net

Peter Eisentraut wrote:

Bruce Momjian - CVS writes:

Modified files:
. : HISTORY

Log message:
Reorder items.

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.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Bruce Momjian writes:

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.

--
Peter Eisentraut peter_e@gmx.net

Peter Eisentraut wrote:

Bruce Momjian writes:

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.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Bruce Momjian <pgman@candle.pha.pa.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

Tom Lane wrote:

Bruce Momjian <pgman@candle.pha.pa.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.

Sure, give me the tools. Right now text format coming out the SGML
tools looks terrible so Peter hacked something up to make it look good.
If we could get that tool into /src/tools I could update release.sgml
and just dump the text file to HISTORY.

I tried using lynx and a few other tools I had here but Peter's was
better. Also keep in mind that it almost always requires a conversion
of the SGML to HTML first, then HTML to text, and that is a 10 minute
process, assuming you have the tools installed. It doesn't seem worth
it.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073