Re: [PATCH] Fix a tiny typo in the documentation - Mailing list pgsql-hackers

From Robin Dupret
Subject Re: [PATCH] Fix a tiny typo in the documentation
Date
Msg-id CA+G124VSzX45n7CdLkXz3EnAAxZNT_WLV8NQbk7wixj=Yh1MFw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Fix a tiny typo in the documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Le mer. 22 janv. 2025 à 16:34, Tom Lane <tgl@sss.pgh.pa.us> a écrit :
>
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
> > On Wednesday, January 22, 2025, Daniel Gustafsson <daniel@yesql.se> wrote:
> >> On 22 Jan 2025, at 11:23, Daniel Gustafsson <daniel@yesql.se> wrote:
> >>> On 22 Jan 2025, at 09:27, Robin Dupret <robin.dupret@gmail.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.



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Add get_bytes() and set_bytes() functions
Next
From: Corey Huinker
Date:
Subject: Re: Extended Statistics set/restore/clear functions.