Date: Mon, 25 Sep 2023 07:00:49 -0500
From: "Karl O. Pinc" <kop@karlpinc.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Various small doc improvements; plpgsql, schemas, permissions,
 oidvector
Message-ID: <20230925070049.456a6d3d@slate.karlpinc.com>
In-Reply-To: <C910C196-A1EF-4497-BC71-864A04E988BD@yesql.se>
References: <20230924175747.2469855f@slate.karlpinc.com>
	<C910C196-A1EF-4497-BC71-864A04E988BD@yesql.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/20230925070049.456a6d3d%40slate.karlpinc.com>
Precedence: bulk

On Mon, 25 Sep 2023 09:26:38 +0200
Daniel Gustafsson <daniel@yesql.se> wrote:

> > On 25 Sep 2023, at 00:57, Karl O. Pinc <kop@karlpinc.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@karlpinc.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein