| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: commitfest.postgresql.org is no longer fit for purpose |
| Date: | 2024-05-17 09:03:54 |
| Message-ID: | CAGECzQSqg1uLGQenOUqtVZR=M8faOR0i9X3Ab7aVH=hOALqisQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 17 May 2024 at 11:02, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
>
> On Fri, 17 May 2024 at 10:47, Daniel Gustafsson <daniel(at)yesql(dot)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(at)postgresql(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey M. Borodin | 2024-05-17 09:11:21 | Re: commitfest.postgresql.org is no longer fit for purpose |
| Previous Message | Jelte Fennema-Nio | 2024-05-17 09:02:45 | Re: commitfest.postgresql.org is no longer fit for purpose |