From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Karl O. Pinc <kop@karlpinc.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences
Date: Fri, 20 Jan 2023 12:42:31 +0100
Message-ID: <20230120114231.ykq5s7w4konrx3i6@alvherre.pgsql> (raw)
In-Reply-To: <20230119120205.55766dd3@slate.karlpinc.com>
On 2023-Jan-19, Karl O. Pinc wrote:
> On Thu, 19 Jan 2023 11:03:53 -0600
> "Karl O. Pinc" <kop@karlpinc.com> wrote:
>
> > Attached are 2 patches, a regular and a delta from your v4 review:
> >
> > contrib_v5-delta.patch.txt
> > contrib_v5.patch.txt
>
> I left your appendix title unchanged: "Additional Supplied
> Extensions and Modules".
>
> I had put "Extensions" after
> "Modules", because, apparently, things that come last in the
> sentence are most remembered by the reader. My impression is that
> more people are looking for extensions than modules.
Hmm, I didn't know that. I guess I can put it back. My own instinct is
to put the most important stuff first, not last, but if research says to
do otherwise, fine, let's do that.
I went over all the titles again. There were a couple of mistakes
and inconsistencies, which I've fixed to the best of my knowledge.
I'm happy with 0001 now and will push shortly unless there are
complaints.
I'm still unsure of the [trusted]/[obsolete] marker, so I split that out
to commit 0002. I would like to see more support for that before
pushing that one.
I also put the page-split bits to another page, because it seems a bit
too clumsy. I hope somebody with more docbook-fu can comment: maybe
there's a way to fix it more generally somehow?
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Update: super-fast reaction on the Postgres bugs mailing list. The report
was acknowledged [...], and a fix is under discussion.
The wonders of open-source !"
https://twitter.com/gunnarmorling/status/1596080409259003906Attachments:
v6-0001-Describe-each-contrib-module-in-its-SGML-section-.patch (text/x-diff, 0B) download
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: alvherre@alvh.no-ip.org, kop@karlpinc.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences
In-Reply-To: <20230120114231.ykq5s7w4konrx3i6@alvherre.pgsql>
* 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