Postgres Pro
Downloads
Home   >   mailing lists

Re: Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.) - Mailing list pgsql-docs

From Robert Haas
Subject Re: Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)
Date
Msg-id CA+TgmobAS1wK7CgjC3bnT8CRscMEkjm2P+Ew9jt7yDTdoen5Vw@mail.gmail.com
Whole thread Raw
In response to Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-docs
Tree view 
On Tue, Feb 4, 2014 at 11:43 PM, Noah Misch <noah@leadboat.com> wrote:
>> Right.  I mean, a lot of the links say things like "Section 26.2"
>> which obviously makes no sense in a standalone text file.
>
> For <xref>s normally displayed that way, text output could emit a URL, either
> inline or in the form of a footnote.  For link targets (e.g. SQL commands)
> having a friendly text fragment for <xref> sites, use the normal fragment.

True.  If we're going to keep these things around, something like that
would avoid some annoyances for documentation authors.  But I still
think we ought to just nuke them, because who cares?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-docs by date:

Previous
From: Robert Haas
Date:
Subject: Re: Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: Re: Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.)