public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jim C. Nasby <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Thomas F.O'Connell <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Version information in docs
Date: Tue, 29 Mar 2005 13:17:47 -0600
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Mon, Mar 28, 2005 at 05:52:30PM -0500, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > Something else that comes to mind... going back to older versions of the
> > manual wouldn't be nearly as tedeous if there were links to older
> > versions somewhere on the pages. Maybe at every section header?
>
> The good thing about our current setup is that all changes are
> centralized in the release notes.
I don't see how my suggestion would necessarily change that. But if
you're trying to figure out when a feature was introduced sifting
through a bunch of release notes seems as bad as sifting through old
versions of the manuals. Or maybe even worse; at least with the manuals
you know what section to look in.
--
Jim C. Nasby, Database Consultant [email protected]
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
view thread (7+ messages)
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: Version information in docs
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