From: Noah Misch <noah@leadboat.com>
To: Karl O. Pinc <kop@karlpinc.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences
Date: Sun, 9 Apr 2023 11:50:50 -0700
Message-ID: <20230409185050.GA949159@rfd.leadboat.com> (raw)
In-Reply-To: <20230330012705.7295be34@slate.karlpinc.com>
References: <20230120191203.7nyqjbw3qe7xx4ru@alvherre.pgsql>
<20230120191238.ds5l4ehuxve4zn42@alvherre.pgsql>
<20230120142225.3d3be8a3@slate.karlpinc.com>
<20230121081143.322bcf9f@slate.karlpinc.com>
<20230122080903.693b171a@slate.karlpinc.com>
<20230122144246.0ff87372@slate.karlpinc.com>
<20230330043205.GA449577@rfd.leadboat.com>
<20230330012705.7295be34@slate.karlpinc.com>
On Thu, Mar 30, 2023 at 01:27:05AM -0500, Karl O. Pinc wrote:
> On Wed, 29 Mar 2023 21:32:05 -0700
> Noah Misch <noah@leadboat.com> wrote:
>
> > On Sun, Jan 22, 2023 at 02:42:46PM -0600, Karl O. Pinc wrote:
> > > v10-0001-List-trusted-and-obsolete-extensions.patch
> >
> > > + <para id="contrib-obsolete">
> > > + These modules and extensions are obsolete:
> > > +
> > > + <simplelist type="inline">
> > > + <member><xref linkend="intagg"/></member>
> > > + <member><xref linkend="xml2"/></member>
> > > + </simplelist>
> > > + </para>
> >
> > Commit a013738 incorporated this change. Since xml2 is the only
> > in-tree way to use XSLT from SQL, I think xml2 is not obsolete. Some
> > individual functions, e.g. xml_valid(), are obsolete. (There are
> > years-old threats to render the module obsolete, but this has never
> > happened.)
>
> Your point seems valid but this is above my station.
> I have no idea as to how to best resolve this, or even how to make the
> resolution happen now that the change has been committed.
I'm inclined to just remove <para id="contrib-obsolete">. While intagg is
indeed obsolete, having a one-entry list seems like undue weight.
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-www@postgresql.org
Cc: noah@leadboat.com, kop@karlpinc.com, alvherre@alvh.no-ip.org, pgsql-hackers@lists.postgresql.org
Subject: Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences
In-Reply-To: <20230409185050.GA949159@rfd.leadboat.com>
* 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