public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jim C. Nasby <[email protected]>
To: Tom Lane <[email protected]>
Cc: Joe Conway <[email protected]>
Cc: [email protected]
Cc: Tino Wildenhain <[email protected]>
Cc: [email protected]
Cc: Andre Truter <[email protected]>
Subject: Re: [Pgsqlrpms-hackers] Re: DBlink documentation
Date: Mon, 19 Dec 2005 15:55:38 -0600
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]>
On Sat, Dec 17, 2005 at 03:47:54PM -0500, Tom Lane wrote:
> It'd be a good idea to settle on what we want the installed file layout
> to be --- do we need to create subdirectories under {prefix}/doc to
> forestall name conflicts?
README is probably fine for most of what's in contrib, but for other
stuff we should support a doc directory. tsearch2 currently has 100k of
HTML in docs, I really don't think we want to cram all that into the
README.
--
Jim C. Nasby, Sr. Engineering Consultant [email protected]
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
view thread (25+ 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], [email protected], [email protected], [email protected]
Subject: Re: [Pgsqlrpms-hackers] Re: DBlink documentation
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