On Mon, 25 Sep 2023 14:14:37 +0200
Daniel Gustafsson <daniel@yesql.se> wrote:
> > 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?
> 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.
Done. 11 patches attached. Thanks for the help.
(This is v2, since I made some changes upon review.)
I am not particularly confident in the top-line commit
descriptions. Some seem kind of long and not a whole
lot of thought went into them. But the commit descriptions
are for the committer to decide anyway.
The bulk of the commit descriptions are very wordy
and will surely need at least some editing.
Listing all the attachments here for future discussion:
v2-0001-Change-section-heading-to-better-reflect-saving-a.patch
v2-0002-Change-section-heading-to-better-describe-referen.patch
v2-0003-Better-section-heading-for-plpgsql-exception-trap.patch
v2-0004-Describe-how-to-raise-an-exception-in-the-excepti.patch
v2-0005-Improve-sentences-in-overview-of-system-configura.patch
v2-0006-Provide-examples-of-listing-all-settings.patch
v2-0007-Cleanup-summary-of-role-powers.patch
v2-0008-Explain-the-difference-between-role-attributes-an.patch
v2-0009-Document-the-oidvector-type.patch
v2-0010-Improve-sentences-about-the-significance-of-the-s.patch
v2-0011-Add-a-sub-section-to-describe-schema-resolution.patch
Regards,
Karl <kop@karlpinc.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
