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 C081530FB02 for ; Wed, 25 Jun 2003 03:20:46 +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 33114-02 for ; Wed, 25 Jun 2003 00:20:36 -0300 (ADT) Received: from tomts9-srv.bellnexxia.net (tomts9.bellnexxia.net [209.226.175.53]) by svr1.postgresql.org (Postfix) with ESMTP id BFD4830F925 for ; Wed, 25 Jun 2003 00:20:35 -0300 (ADT) Received: from [192.168.1.200] ([216.209.81.133]) by tomts9-srv.bellnexxia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20030625032034.ZUCX12086.tomts9-srv.bellnexxia.net@[192.168.1.200]>; Tue, 24 Jun 2003 23:20:34 -0400 Subject: Re: Current CVS docs producing errors From: Rod Taylor To: Bruno Wolff III Cc: PostgreSQL Docs In-Reply-To: <20030625031856.GA3521@wolff.to> References: <20030625025232.GA31072@wolff.to> <1056509551.69651.23.camel@jester> <20030625031856.GA3521@wolff.to> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-LVZycVPNsnxxKoAvGyT+" Message-Id: <1056511251.69651.33.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 24 Jun 2003 23:20:52 -0400 X-Archive-Number: 200306/53 X-Sequence-Number: 1839 --=-LVZycVPNsnxxKoAvGyT+ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2003-06-24 at 23:18, Bruno Wolff III wrote: > On Tue, Jun 24, 2003 at 22:52:32 -0400, > Rod Taylor wrote: > > Seems you were caught in mid patch. > >=20 > > They work with cvs sources from 30 minutes ago. > >=20 > > Try updating and re-running -- the last error in particular was caused > > by 2 patches crossing in the night (patch queue). >=20 > I resynced and picked up a new perform.sgml and TODO.sgml. This got rid > of one of the errors. I am still seeing all of the datatype.sgml errors. > I wasn't getting these errors a couple of days ago. Are you sure you don't have local changes? A conflict perhaps? Try removing datatype.sgml and re-fetching it again. Below is the only change to that file in a number of days, and it looks fine to me. http://developer.postgresql.org/cvsweb.cgi/pgsql-server/doc/src/sgml/dataty= pe.sgml.diff?r1=3D1.117&r2=3D1.118 --=20 Rod Taylor PGP Key: http://www.rbt.ca/rbtpub.asc --=-LVZycVPNsnxxKoAvGyT+ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA++RUT6DETLow6vwwRApMJAJ4k/M7YFTeVsi6ntMrMIyTNaogMwgCcDWQO KGeWgLvJNl52qzPHLmMavuE= =IRIu -----END PGP SIGNATURE----- --=-LVZycVPNsnxxKoAvGyT+--