| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pspung(at)northcarolina(dot)edu, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Typo |
| Date: | 2023-05-23 23:44:26 |
| Message-ID: | CAKFQuwZbQLq-bmoaQo_NB9TpouABPm9R0s=H9se+ckex5Y-r-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tue, May 23, 2023 at 3:32 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Tue, May 23, 2023 at 08:52:25PM +0000, PG Doc comments form wrote:
> > There appears to be a typo, here:
> >
> https://www.postgresql.org/docs/current/history.html#:~:text=Postgres95%20code%20was%20completely%20ANSI%20C
> .
> > A word or two should be added between 'completely' and 'ANSI C', such as
> > 're-written in', or 're-coded using', or some such.
>
> This is the current sentence, and it sounds kind of OK to me, FWIW:
> "Postgres95 code was completely ANSI C and trimmed in size by 25%.
>
>
I agree with the OP, that is missing something. Maybe:
Between the 4.2 release and the release of Postgres95 the code was made to
completely adhere to ANSI C and the size was reduced by 25%.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-05-24 04:02:27 | Re: Typo |
| Previous Message | Michael Paquier | 2023-05-23 22:32:22 | Re: Typo |