public inbox for [email protected]  

help / color / mirror / Atom feed

From: Karl O. Pinc <[email protected]>
To: Daniel Gustafsson <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector
Date: Mon, 25 Sep 2023 07:00:49 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Mon, 25 Sep 2023 09:26:38 +0200
Daniel Gustafsson <[email protected]> wrote:

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

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox