Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector
Date
Msg-id BF64D5ED-EAFF-4C1F-A78A-90773C835F81@yesql.se
Whole thread Raw
In response to Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector  ("Karl O. Pinc" <kop@karlpinc.com>)
Responses Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector
List pgsql-hackers
> On 25 Sep 2023, at 14:00, Karl O. Pinc <kop@karlpinc.com> wrote:

> Is there a preferred data format or should I send
> each patch in a separate attachment with description?

The easiest way would be to create a patchset off of master I think.  In a
branch, commit each change with an explanatory commit message.  Once done you
can do "git format-patch origin/master -v 1" which will generate a set of n
patches named v1-0001 through v1-000n.  You can then attache those to the
thread.  This will make it easier for a reviewer, and it's easy to apply them
in the right order in case one change depends on another earlier change.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: "Karl O. Pinc"
Date:
Subject: Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector
Next
From: Daniel Gustafsson
Date:
Subject: Re: GUC for temporarily disabling event triggers