pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Cc: Andrew Dunstan <andrew@dunslane.net>
Subject: Re: PG documentation build is wedged
Date: Thu, 24 Nov 2011 00:32:02 -0300
Message-ID: <1322104954-sup-6925@alvh.no-ip.org> (raw)
In-Reply-To: <10331.1322103322@sss.pgh.pa.us>
References: <10331.1322103322@sss.pgh.pa.us>


Excerpts from Tom Lane's message of mié nov 23 23:55:22 -0300 2011:
> According to
> http://developer.postgresql.org/pgdocs/postgres/buildlog.html
> the git-tip documentation build hasn't happened since the 19th,
> and a quick look-around at
> http://developer.postgresql.org/pgdocs/postgres/index.html
> confirms that recent docs changes don't seem to be showing there.

I think the devel docs are now supposed to be built by bf member
guaibasaurus, but the necessary hooks on the buildfarm client to copy
them to the webserver aren't there yet.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



view thread (7+ messages)  latest in thread

Message-ID: <1322104954-sup-6925@alvh.no-ip.org>
Permalink:  ../1322104954-sup-6925@alvh.no-ip.org/
Also on:    postgresql.org/message-id/1322104954-sup-6925@alvh.no-ip.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: alvherre@commandprompt.com, tgl@sss.pgh.pa.us, peter_e@gmx.net, andrew@dunslane.net
  Subject: Re: PG documentation build is wedged
  In-Reply-To: <1322104954-sup-6925@alvh.no-ip.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