Re: Commitfest 2023-03 starting tomorrow! - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Commitfest 2023-03 starting tomorrow!
Date
Msg-id CAM-w4HM8EDXVWF9rHAF9bxXZwyTDEudmykpWkq8JEL9EN_XqPw@mail.gmail.com
Whole thread Raw
In response to Re: Commitfest 2023-03 starting tomorrow!  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Commitfest 2023-03 starting tomorrow!  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
The next level of this would be something like notifying the committer
with a list of patches in the CF that a commit broke. I don't
immediately see how to integrate that with our workflow but I have
seen something like this work well in a previous job. When committing
code you often went and updated other unrelated projects to adapt to
the new API (or could adjust the code you were committing to cause
less breakage).



pgsql-hackers by date:

Previous
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: Memory leak from ExecutorState context?
Next
From: Tom Lane
Date:
Subject: Re: Missing rules for queryjumblefuncs.{funcs,switch}.c for maintainer-clean