Re: Assorted small doc patches - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Assorted small doc patches
Date
Msg-id CAKFQuwYTX3-sXLU1_HVcB_ocJAMyHb9L9ohm4s9wdDxUnvT-pQ@mail.gmail.com
Whole thread Raw
In response to Re: Assorted small doc patches  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Wed, Jun 1, 2022 at 7:05 AM Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
On 31.05.22 22:12, David G. Johnston wrote:
> Anything I should be doing differently here to get a bit of
> reviewer/committer time on these?  I'll add them to the commitfest for
> next month if needed but I'm seeing quick patches going in every week
> and the batch format done at the beginning of the month got processed
> through without issue.
 
 It might have been better to post these
separately.


Doing so hasn't seemed to make a difference.  Still not getting even a single committer on a single patch willing to either work with me to get it committed, or decide otherwise, despite my prompt responses on the few comments that have been given.

Given the lack of feedback and my track record I don't think it unreasonable for someone to simply commit these without comment and let any late naysayers voice their opinions after it hits the repo.

In any case, I've added these and more to the commitfest at this point so hopefully the changed mindset of committers when it comes to clearing out the commitfest backlog will come into play in a couple of weeks and I might see some action.

David J.

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: CFM for 2022-07
Next
From: Greg Stark
Date:
Subject: Re: Remove trailing newlines from pg_upgrade's messages