X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id D0B3D30FB36 for ; Wed, 25 Jun 2003 03:51:34 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 33100-06 for ; Wed, 25 Jun 2003 00:51:24 -0300 (ADT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id B806730FB29 for ; Wed, 25 Jun 2003 00:51:23 -0300 (ADT) Received: (qmail 16725 invoked by uid 500); 25 Jun 2003 03:54:47 -0000 Date: Tue, 24 Jun 2003 22:54:47 -0500 From: Bruno Wolff III To: Rod Taylor , PostgreSQL Docs Subject: Re: Current CVS docs producing errors Message-ID: <20030625035447.GB12552@wolff.to> Mail-Followup-To: Rod Taylor , PostgreSQL Docs References: <20030625025232.GA31072@wolff.to> <1056509551.69651.23.camel@jester> <20030625031856.GA3521@wolff.to> <1056511251.69651.33.camel@jester> <20030625033850.GA12404@wolff.to> <20030625034808.GA12552@wolff.to> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <20030625034808.GA12552@wolff.to> User-Agent: Mutt/1.5.4i X-Archive-Number: 200306/57 X-Sequence-Number: 1843 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline These changes fixed the problem I was having. --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=temp *** 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:4f8:3:ba::/64 2001:4f8:3:ba::/64 *************** *** 2622,2631 **** --- 2623,2634 ---- ::ffff:1.2.3.0/120 ::ffff:1.2.3.0/120 ::ffff:1.2.3/120 + ::ffff:1.2.3.0/128 ::ffff:1.2.3.0/128 ::ffff:1.2.3.0/128 + --Qxx1br4bt0+wmkIi--