From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Snapshots no longer build |
Date: | 2011-01-29 18:35:52 |
Message-ID: | AANLkTi=Kb_HHzfAETCu1OAqYZyHN7qVTkYcVNg5bN6AD@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 29 January 2011 17:58, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thom Brown <thom(at)linux(dot)com> writes:
>> On 29 January 2011 11:12, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> Any idea why this is happening?
>
>> I don't know what's causing that since I can see both of those IDs are
>> present, but I should also mention that the identities those linkends
>> point to should have xreflabel attributes. At the moment, it's
>> reading: "Use the OSSP UUID library when building the Section F.44
>> module"
>
> Yeah, that is pretty icky, and Bruce introduced similar unpleasantness
> in a bunch of places. I'm unsure that xreflabel is a good fix, though,
> because there are other places where the wording is such that a
> chapter/section number reference *is* appropriate, eg a parenthetical
> cross-reference "(see <xref>)".
Okay, I see why that's a problem.
> I think what we might need is to use <link linkend="xml2">xml2</link>
> in the places where we want the xref to read as an incidental hyperlink
> rather than a cross-reference. Comments?
Sure, that would work.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-01-29 18:39:54 | SPI_exec doesn't return proc context (on 9.1) |
Previous Message | Peter Eisentraut | 2011-01-29 18:34:01 | Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state |