Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Bruno Wolff III
On Tue, Jun 24, 2003 at 23:51:02 -0400, Bruce Momjian <[EMAIL PROTECTED]> wrote: > > Found them --- patch applied. Thanks. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Bruno Wolff III
These changes fixed the problem I was having. *** datatype.sgml.orig Tue Jun 24 22:41:31 2003 --- datatype.sgml Tue Jun 24 22:42:44 2003 *** *** 2608,2613 --- 2608,2614 10.1.2.3/32 10.1.2.3/32 10.1.2.3/32 + 2001:

Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Bruce Momjian
Found them --- patch applied. --- Bruno Wolff III wrote: > On Tue, Jun 24, 2003 at 22:38:50 -0500, > Bruno Wolff III <[EMAIL PROTECTED]> wrote: > > > > I looked at this and while I don't know SGML I expect that the compla

Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Bruno Wolff III
On Tue, Jun 24, 2003 at 22:38:50 -0500, Bruno Wolff III <[EMAIL PROTECTED]> wrote: > > I looked at this and while I don't know SGML I expect that the complaints > are referring to some unclosed entries that were added in that change. > They are in the last section of the differences (after line

Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Bruno Wolff III
On Tue, Jun 24, 2003 at 23:20:52 -0400, Rod Taylor <[EMAIL PROTECTED]> wrote: > > Are you sure you don't have local changes? A conflict perhaps? I had wiped what I had tonight to get a clean copy from CVS as I had been testing a patch to fix some problems with sockaddr and wanted to see if thin

Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Rod Taylor
On Tue, 2003-06-24 at 23:18, Bruno Wolff III wrote: > On Tue, Jun 24, 2003 at 22:52:32 -0400, > Rod Taylor <[EMAIL PROTECTED]> wrote: > > Seems you were caught in mid patch. > > > > They work with cvs sources from 30 minutes ago. > > > > Try updating and re-running -- the last error in particul

Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Bruno Wolff III
On Tue, Jun 24, 2003 at 22:52:32 -0400, Rod Taylor <[EMAIL PROTECTED]> wrote: > Seems you were caught in mid patch. > > They work with cvs sources from 30 minutes ago. > > Try updating and re-running -- the last error in particular was caused > by 2 patches crossing in the night (patch queue).

Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Bruce Momjian
It works here and in the 15 minute build in the developers site. --- Bruno Wolff III wrote: > When building postgres.tar.gz I get the following errors: > > make -C sgml clean > make[1]: Entering directory `/usr/local/src/po

Re: [DOCS] Current CVS docs producing errors

2003-06-24 Thread Rod Taylor
Seems you were caught in mid patch. They work with cvs sources from 30 minutes ago. Try updating and re-running -- the last error in particular was caused by 2 patches crossing in the night (patch queue). On Tue, 2003-06-24 at 22:52, Bruno Wolff III wrote: > When building postgres.tar.gz I get t

[DOCS] Current CVS docs producing errors

2003-06-24 Thread Bruno Wolff III
When building postgres.tar.gz I get the following errors: make -C sgml clean make[1]: Entering directory `/usr/local/src/postgresql-7.4/pgsql/doc/src/sgml' rm -f HTML.manifest *.html *.gif rm -rf *.1 *.l man1 manl manpage.refs manpage.links manpage.log rm -f *.rtf *.tex-ps *.tex-pdf *.dvi *.aux *.

Re: [DOCS] [PATCHES] Synopsis inconsistencies

2003-06-24 Thread Bruce Momjian
Patch applied. Thanks. --- Rod Taylor wrote: -- Start of PGP signed section. > Most of the synopsis areas for DROP commands use "name" as the > identifier, while some areas do not. > > The attached converts be below to "n

Re: [DOCS] [GENERAL] [pgsql-advocacy] Documentation quality WAS: interesting

2003-06-24 Thread nolan
> Agreed. I am starting a list of what can/need to be indexed on pgsql docs > site as I'm working to build a new site with pgsql as a backend. I > think Tom Lane > suggested that.. I would like to know where I can send > the list. It'll probably somekind of a work in progress. So if everyone >