public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dan Langille <[email protected]>
To: Tom Lane <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: [HACKERS] What goes into the security doc?
Date: Wed, 03 Sep 2003 13:54:01 -0400
Message-ID: <3F55F279.28486.43EEB095@localhost> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On 30 Aug 2003 at 17:50, Tom Lane wrote:

> Bruce Momjian <[email protected]> writes:
> > I don't think we "decided" to add it, but no one has objected to the
> > idea, except Peter recently.  Does it make sense to have a security
> > overview section in the documentation?
> 
> I think it does.
> 
> As I think Peter is trying to point out, you could almost get the same
> result just by having a fat index entry under "security", but I think
> people are more likely to notice a chapter or section in the Admin Guide
> with such a title.  Also, once we have such a chapter, we might find it
> reads more naturally to move some of the existing discussions into it,
> leaving only a cross-reference where the material is now.

So do we want this work or not?
-- 
Dan Langille : http://www.langille.org/

view thread (20+ 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]
  Subject: Re: [HACKERS] What goes into the security doc?
  In-Reply-To: <3F55F279.28486.43EEB095@localhost>

* 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