| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Greg Stark <stark(at)mit(dot)edu>, "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-18 23:28:02 |
| Message-ID: | CAH2-Wzk+K54T_igU0BGS8JVYvJ1Tm7E2Wz=DsZ==UJNG=DrgDw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 18, 2023 at 4:19 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> The only issue with this is that cfbot has squished all the commits into
> one, and lost the original commit messages (if any). I submitted
> patches to address that but still waiting for feedback.
>
> https://www.postgresql.org/message-id/20220623193125.GB22452@telsasoft.com
Right. I would like to see that change. But you still need to have CF
tester/the CF app remember the last master branch commit that worked
before bitrot. And you have to provide an easy way to get that
information.
I generally don't care if that means that I have to initdb - I do that
all the time. It's a small price to pay for a workflow that I know is
practically guaranteed to get me a usable postgres executable on the
first try, without requiring any special effort. I don't want to even
think about bitrot until I'm at least 10 minutes into looking at
something.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2023-03-18 23:44:29 | Re: Commitfest 2023-03 starting tomorrow! |
| Previous Message | Justin Pryzby | 2023-03-18 23:19:47 | Re: Commitfest 2023-03 starting tomorrow! |