From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Dan Stoner <danstoner(at)gmail(dot)com> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: streaming replication depends on matching glibc versions / LOCALE sort order |
Date: | 2023-08-08 19:47:00 |
Message-ID: | 4ccdfd24-e5fc-88a5-ad2e-567042da2b7d@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 8/8/23 15:05, Dan Stoner wrote:
> I'm circling back around to this.
>
> I've cloned the postgresql git repo and started looking thru
> doc/src/sgml directory, looking thru the developer FAQ on the wiki,
> etc.
>
> For documentation updates such as this, where would I submit the
> patch(es)? Is the process the same as other code commits?
>
> https://wiki.postgresql.org/wiki/Submitting_a_Patch
Yes. Basically send a patch
(https://wiki.postgresql.org/wiki/Creating_Clean_Patches) with your
changes to the list and register the patch for the next "Open" commitfest:
https://commitfest.postgresql.org/
Currently:
2023-09 (Open - 2023-09-01 - 2023-09-30)
"Open" means it is open for submission of patches to be considered, and
the dates (all of September) are the beginning and end of the commitfest
during which the patch would be reviewed, discussed, and hopefully
committed. Once the Commitfest is started (2023-09-01) it is no longer
Open for new submissions (I forget the exact state name, but it is
In-progress or something similar)
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2023-08-10 07:55:53 | Include PostgresNIO Swift client in the Documentation |
Previous Message | Dan Stoner | 2023-08-08 19:05:17 | Re: streaming replication depends on matching glibc versions / LOCALE sort order |