Re: Commit fest 2022-11

From: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, Michael Paquier <michael(at)paquier(dot)xyz>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, david(dot)christensen(at)crunchydata(dot)com, rjuju123(at)gmail(dot)com, vignesh21(at)gmail(dot)com, bharath(dot)rupireddyforpostgres(at)gmail(dot)com, jtc331(at)gmail(dot)com, sh95119(at)gmail(dot)com, d(dot)koval(at)postgrespro(dot)ru, sawada(dot)mshk(at)gmail(dot)com
Subject: Re: Commit fest 2022-11
Date: 2022-11-14 12:08:46
Message-ID: CAB8KJ=i3zg7d=gt0z5WLo-ui1QYDQ6VdWk1X00suyygGVYLNPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2022年11月9日(水) 8:12 Justin Pryzby <pryzby(at)telsasoft(dot)com>:
>
> On Thu, Nov 03, 2022 at 07:43:03PM -0500, Justin Pryzby wrote:
> > On Thu, Nov 03, 2022 at 11:33:57AM +0900, Ian Lawrence Barwick wrote:
> > > 2022年11月2日(水) 19:10 Greg Stark <stark(at)mit(dot)edu>:
> > > > On Tue, 1 Nov 2022 at 06:56, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> > > >
> > > > > Two people showing up to help is really great, thanks! I'll be around
> > > > > as well this month, so I'll do my share of patches, as usual.
> > > >
> > > > Fwiw I can help as well -- starting next week. I can't do much this week though.
> > > >
> > > > I would suggest starting with the cfbot to mark anything that isn't
> > > > applying cleanly and passing tests (and looking for more than design
> > > > feedback) as Waiting on Author and reminding the author that it's
> > > > commitfest time and a good time to bring the patch into a clean state.
> > >
> > > Sounds like a plan; I'll make a start on that today/tomorrow as I have
> > > some time.
> >
> > If I'm not wrong, Jacob used the CF app to bulk-mail people about
> > patches not applying and similar things. That seemed to work well, and
> > doesn't require sending mails to dozens of threads.
>
> If my script is not wrong, these patches add TAP tests, but don't update
> the requisite ./meson.build file. It seems like it'd be reasonable to
> set them all as WOA until that's done.
>
> $ for a in `git branch -a |sort |grep commitfest/40`; do : echo "$a..."; x=`git log -1 --compact-summary "$a"`; echo "$x" |grep '/t/.*pl.*new' >/dev/null || continue; echo "$x" |grep -Fw meson >/dev/null && continue; git log -1 --oneline "$a"; done
> ... [CF 40/3558] Allow file inclusion in pg_hba and pg_ident files
> ... [CF 40/3628] Teach pg_waldump to extract FPIs from the WAL stream
> ... [CF 40/3646] Skip replicating the tables specified in except table option
> ... [CF 40/3663] Switching XLog source from archive to streaming when primary available
> ... [CF 40/3670] pg_rewind: warn when checkpoint hasn't happened after promotion
> ... [CF 40/3729] Testing autovacuum wraparound
> ... [CF 40/3877] vacuumlo: add test to vacuumlo for test coverage
> ... [CF 40/3985] TDE key management patches

Looks like your script is correct, will update accordingly.

Do we have a FAQ/checklist of meson things to consider for patches anywhere?

Regards

Ian Barwick

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2022-11-14 12:36:56 Re: pg_basebackup's --gzip switch misbehaves
Previous Message Melih Mutlu 2022-11-14 12:07:30 Re: Allow logical replication to copy tables in binary format