public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Scott Marlowe <[email protected]>
Cc: Euler Taveira de Oliveira <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: Inheritance mention
Date: Mon, 13 Apr 2009 13:21:46 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Scott Marlowe <[email protected]> writes:
> On Mon, Apr 13, 2009 at 12:04 AM, Tom Lane <[email protected]> wrote:
>> Pre-7.1 might indeed be old enough to cut, but how much are we really
>> saving? �Four sentences out of our current docs doesn't excite me ...

> But since there's a doc set per version, it would make sense to stop
> mentioning unsupported versions in the docs for supported versions,
> no?  Or is this a FAQ thing we're talking about?

The problem is what to tell people to read if they want to transition
from an unsupported version to a supported version.

If we really wanted to save some space, we could cut all the release
notes for pre-7.4 (soon pre-8.0) releases.  But somehow that doesn't
seem like a good idea.  What it would mainly accomplish is to make it
hard to find the old information when you wanted it.

			regards, tom lane

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: Inheritance mention
  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