Re: commitfest.postgresql.org is no longer fit for purpose - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: commitfest.postgresql.org is no longer fit for purpose
Date
Msg-id CAGECzQSqg1uLGQenOUqtVZR=M8faOR0i9X3Ab7aVH=hOALqisQ@mail.gmail.com
Whole thread Raw
In response to Re: commitfest.postgresql.org is no longer fit for purpose  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers
On Fri, 17 May 2024 at 11:02, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
>
> On Fri, 17 May 2024 at 10:47, Daniel Gustafsson <daniel@yesql.se> wrote:
> > One way to ensure we capture detail could be if the system would send an
> > automated email to the thread summarizing the entry when it's marked as
> > "committed"?
>
> This sounds great! Especially if

(oops pressed send too early)
**Especially if it contains the git commit hash**

> Going back from an archived thread
> to the commitfest entry or git commit is currently very hard. If I'll
> just be able to Ctrl+F on commitfest@postgresql.com that would be so
> helpful. I think it would even be useful to have an email be sent
> whenever a patch gets initially added to the commitfest, so that
> there's a back link to and it's easy to mark yourself as reviewer.
> Right now, I almost never take the time to do that because if I look
> at my inbox, I have no clue what the interesting email thread is
> called in the commitfest app.



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Next
From: "Andrey M. Borodin"
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose