| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| 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:44:29 |
| Message-ID: | ZBZM3del8fEC13eE@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 18, 2023 at 04:28:02PM -0700, Peter Geoghegan wrote:
> 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.
No - the last in cfbot's repo is from the last time it successfully
applied the patch. You can summarily check checkout cfbot's branch to
build (or just to git log -p it, if you dislike github's web interface).
If you're curious and still wanted to know what commit it was applied
on, it's currently the 2nd commit in "git log" (due to squishing
all patches into one).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-03-19 01:32:05 | Re: buildfarm + meson |
| Previous Message | Peter Geoghegan | 2023-03-18 23:28:02 | Re: Commitfest 2023-03 starting tomorrow! |