X-Original-To: pgsql-docs@postgresql.org
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id E3CB8475B47
	for <pgsql-docs@postgresql.org>; Sun,  9 Mar 2003 13:14:58 -0500 (EST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h29IElub020059;
	Sun, 9 Mar 2003 13:14:47 -0500 (EST)
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Rod Taylor <rbt@rbt.ca>, Bruce Momjian <pgman@candle.pha.pa.us>,
	pgsql-docs@postgresql.org
Subject: Re: Documentation TODO list 
In-reply-to: <Pine.LNX.4.44.0303082141130.2390-100000@peter.localdomain> 
References: <Pine.LNX.4.44.0303082141130.2390-100000@peter.localdomain>
Comments: In-reply-to Peter Eisentraut <peter_e@gmx.net>
	message dated "Sun, 09 Mar 2003 17:24:42 +0100"
Date: Sun, 09 Mar 2003 13:14:47 -0500
Message-ID: <20058.1047233687@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200303/20
X-Sequence-Number: 1698

Peter Eisentraut <peter_e@gmx.net> writes:
> All of these things are already done in my local copy.  I'm currently
> preparing the documentation for a book publisher, so I've been
> accumulating a rather massive amount of these kinds of fixes.  I think
> once they've passed by the other reviewers involved in this process I'll
> commit them.

I'd suggest committing sooner rather than later, or you are going to
suffer a daunting merge problem.  You don't think the CVS docs are going
to hold still for long, do you?

I've watched tech writers at both Great Bridge and Red Hat make exactly
this mistake: accumulate huge amounts of editorial fixes, and then
discover that there wasn't any practical way to merge with the community
docs when it came time to do so --- because the community docs had
diverged from what they started from.  Please don't follow in their
footsteps.

			regards, tom lane

PS: a book project sounds cool.  Can you give any details?