From: | "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector |
Date: | 2023-09-25 12:00:49 |
Message-ID: | 20230925070049.456a6d3d@slate.karlpinc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 25 Sep 2023 09:26:38 +0200
Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > On 25 Sep 2023, at 00:57, Karl O. Pinc <kop(at)karlpinc(dot)com> wrote:
>
> > I have made various, mostly unrelated to each other,
> > small improvements to the documentation.
> While I agree it's subjective, I don't think adding a new section or
> paragraph qualifies as short or small. I would prefer if each
> (related) change is in a single commit with a commit message which
> describes the motivation for the change. A reviewer can second-guess
> the rationale for the changes, but they shouldn't have to.
Will do. Is there a preferred data format or should I send
each patch in a separate attachment with description?
> The resulting patchset can all be in the same thread though.
Thanks.
Regards,
Karl <kop(at)karlpinc(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2023-09-25 12:14:37 | Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector |
Previous Message | Nazir Bilal Yavuz | 2023-09-25 11:56:28 | Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs |