Re: [PATCH] Fix a tiny typo in the documentation

From: Robin Dupret <robin(dot)dupret(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Fix a tiny typo in the documentation
Date: 2025-01-23 14:42:06
Message-ID: CA+G124VSzX45n7CdLkXz3EnAAxZNT_WLV8NQbk7wixj=Yh1MFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le mer. 22 janv. 2025 à 16:34, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :
>
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > On Wednesday, January 22, 2025, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> >> On 22 Jan 2025, at 11:23, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> >>> On 22 Jan 2025, at 09:27, Robin Dupret <robin(dot)dupret(at)gmail(dot)com> wrote:
> >>>> - special provision: you must write
> >>>> + special provision you must write:
>
> But like David, I don't feel a need to change anything here. There
> are many places in our docs where we flow into a <programlisting> or
> similar block without punctuation, and most of them read just fine
> to me.
>
Yes, you're right. On the other hand, it is very common to see a colon
right before a block with code or error message so maybe changing it
for a semi-colon or period would make reading less "odd".

But anyway, I'm fine if you leave it as is. :-)
Thanks for your time.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2025-01-23 14:51:08 Re: Extended Statistics set/restore/clear functions.
Previous Message Aleksander Alekseev 2025-01-23 14:30:19 Re: [PATCH] Add get_bytes() and set_bytes() functions