Re: cfbot wrangling (was Re: Add checkpoint and redo LSN to LogCheckpointEnd log message) - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: cfbot wrangling (was Re: Add checkpoint and redo LSN to LogCheckpointEnd log message)
Date
Msg-id CA+hUKGL1zcQj0VM_-uxNUOTFv7W0LNjvaV13cYTFSTS_6xH4qg@mail.gmail.com
Whole thread Raw
In response to Re: cfbot wrangling (was Re: Add checkpoint and redo LSN to LogCheckpointEnd log message)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: cfbot wrangling (was Re: Add checkpoint and redo LSN to LogCheckpointEnd log message)
Re: cfbot wrangling (was Re: Add checkpoint and redo LSN to LogCheckpointEnd log message)
List pgsql-hackers
On Wed, Jan 12, 2022 at 7:37 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Julien Rouhaud <rjuju123@gmail.com> writes:
> > On Wed, Jan 12, 2022 at 01:19:22AM -0500, Tom Lane wrote:
> >> 2. You are attaching some random files, and would like to not
> >> displace the cfbot's idea of the latest patchset.
>
> > I'm assuming that someone wanting to send an additional patch to be applied on
> > top of the OP patchset is part of 2?
>
> AFAIK, if you're submitting a patch then you have to attach a complete
> patchset, or the cfbot will be totally lost.  Getting the bot to
> understand incremental patches would be useful for sure ... but it's
> outside the scope of what I'm asking for now, which is just clear
> documentation of what the bot can do already.

By way of documentation, I've just now tried to answer these question
in the new FAQ at:

https://wiki.postgresql.org/wiki/Cfbot



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: cfbot wrangling (was Re: Add checkpoint and redo LSN to LogCheckpointEnd log message)
Next
From: Julien Rouhaud
Date:
Subject: Re: [PATCH] Proof of concept for GUC improvements