From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200403060301.i2631WP00802@candle.pha.pa.us>
Subject: Re: pgsql-server/doc/src/sgml Makefile
In-Reply-To: <10067.1078517250@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 5 Mar 2004 22:01:32 -0500 (EST)
Cc: pgsql-committers@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Tom Lane wrote:
> momjian@svr1.postgresql.org (Bruce Momjian) writes:
> > 	Use '-' for stdin on lynx, my lynx version doesn't support -stdin.
> 
> How old is your lynx?  I checked before making that patch, and -stdin
> seemed to be in the oldest lynx I had handy (RHL 8.0).

I am using:

	Lynx Version 2.8.3rel.1 (23 Apr 2000)

I assume bsdi kept that version perhaps because newer versions had
troubles with some things.

In the old days, only I did HISTORY.  Now that others are doing it,
which is good, we should standardize to prevent CVS from recording
massive changes to HISTORY for different versions of lynx.

> BTW, I recently installed 2.8.5rel.1 here, and it generates very clean
> text output --- no weird trailing spaces, proper justification of
> headings, etc.  I'd suggest standardizing on that for building the
> HISTORY file.

I see on postgresql.org:

	Lynx Version 2.8.5dev.16 (01 Jun 2003)

I used that to generate HISTORY, and I did a diff against the HISTORY I
generated, and the only difference is that it doesn't have spaces on
blank lines, which is even better output than mine.

In the future, I will use postgresql.org lynx.  If you find yours
generates similar output to that, you can keep using your local one.

I have changed the lynx flag back to -stdin, and regenerated HISTORY, so
you can run a comparison with CVS to see if yours is similar.

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