public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Rod Taylor <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: [email protected]
Subject: Re: Documentation TODO list
Date: Sun, 09 Mar 2003 13:14:47 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Peter Eisentraut <[email protected]> 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?

view thread (6+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Documentation TODO list
  In-Reply-To: <[email protected]>

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

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