pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas Lockhart <lockhart@fourpalms.org>
To: Vince Vielhaber <vev@michvhf.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Marc G. Fournier <scrappy@hub.org>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: CVS changes
Date: Tue, 02 Oct 2001 01:14:00 +0000
Message-ID: <3BB914D8.BF38583E@fourpalms.org> (raw)
References: <Pine.BSF.4.30.0110012033540.391-100000@paprika.michvhf.com>

...
> Tom, what's missing or out of place?  If I can I'll make sure it's there.
> This morning I noticed a number of things that I thought were there really
> weren't.

What I was looking for was the place where development docs (built from
daily snapshots) would go. They used to be underneath devel-corner in a
doc(s ??) directory.

I guess I would also expect to find, somewhere, the as-released docs for
current (and previous?) versions.

I was looking the other day and didn't see any of the signs I would have
expected like html files from the docs build process.

Since I don't feel like I understand what the new layout actually is, it
would be nice to hear where I would *expect* to find these things.
"devel-corner is history", "users-lounge is history" lead me to believe
that structure is changing, but I don't know to what.

There are only a few places that I care about (the online docs area is
one of those). I'm happy to wait until new locations are available, but
a quick explanation of where that might be would give me a warm fuzzy
that I'm not falling behind and that I can predict whether the new
layout requires changes to my doc building scripts (as an example).

                        - Thomas



view thread (70+ messages)  latest in thread

Message-ID: <3BB914D8.BF38583E@fourpalms.org>
Permalink:  ../3BB914D8.BF38583E@fourpalms.org/
Also on:    postgresql.org/message-id/3BB914D8.BF38583E@fourpalms.org

 · 

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: pgsql-docs@postgresql.org
  Cc: lockhart@fourpalms.org, vev@michvhf.com, pgman@candle.pha.pa.us, peter_e@gmx.net, scrappy@hub.org, pgsql-hackers@postgresql.org
  Subject: Re: CVS changes
  In-Reply-To: <3BB914D8.BF38583E@fourpalms.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox