pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <rbt@rbt.ca>
To: Bruno Wolff III <bruno@wolff.to>
Cc: PostgreSQL Docs <pgsql-docs@postgresql.org>
Subject: Re: Current CVS docs producing errors
Date: 24 Jun 2003 23:20:52 -0400
Message-ID: <1056511251.69651.33.camel@jester> (raw)
In-Reply-To: <20030625031856.GA3521@wolff.to>
References: <20030625025232.GA31072@wolff.to>
	<1056509551.69651.23.camel@jester>
	<20030625031856.GA3521@wolff.to>

On Tue, 2003-06-24 at 23:18, Bruno Wolff III wrote:
> On Tue, Jun 24, 2003 at 22:52:32 -0400,
>   Rod Taylor <rbt@rbt.ca> 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).
> 
> 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/datatype.sgml.diff?r1=1.117&...
-- 
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

Attachments:

  signature.asc (application/pgp-signature, 186B) download

view thread (10+ messages)  latest in thread

Message-ID: <1056511251.69651.33.camel@jester>
Permalink:  ../1056511251.69651.33.camel@jester/
Also on:    postgresql.org/message-id/1056511251.69651.33.camel@jester

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: rbt@rbt.ca, bruno@wolff.to
  Subject: Re: Current CVS docs producing errors
  In-Reply-To: <1056511251.69651.33.camel@jester>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox