| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Commitfest 2023-03 starting tomorrow! |
| Date: | 2023-03-20 14:14:47 |
| Message-ID: | CAM-w4HM8EDXVWF9rHAF9bxXZwyTDEudmykpWkq8JEL9EN_XqPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-03-20 14:21:28 | Re: Missing rules for queryjumblefuncs.{funcs,switch}.c for maintainer-clean |
| Previous Message | Jehan-Guillaume de Rorthais | 2023-03-20 14:12:34 | Re: Memory leak from ExecutorState context? |