public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Joe Conway <[email protected]>
Cc: Jim C. Nasby <[email protected]>
Cc: [email protected]
Cc: Tino Wildenhain <[email protected]>
Cc: Andre Truter <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: Supplemental contrib docs
Date: Wed, 04 Jan 2006 00:03:56 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Joe Conway <[email protected]> writes:
> Well, I assumed Tom was referring to placement in the source tree, i.e. 
> {prefix} is contrib/dblink, etc.

I'm concerned about both location in the source tree (dblink and
tsearch2 are inconsistent) and location in the installation tree.
The former seems easy to resolve: doc/ is the universal standard
directory name for documentation, not docs/.  I am not sure that
we want to commit to creating a pile of subdirectories under the
installation doc/ directory, though.  If they were mostly full,
fine, but a bunch of directories that are mostly empty would just
be clutter.  Maybe create subdirectories only for modules that
have 'em in the source tree?

			regards, tom lane

view thread (25+ 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], [email protected], [email protected]
  Subject: Re: Supplemental contrib 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