Re: adding the commit to a patch's thread

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Erik Rijkers <er(at)xs4all(dot)nl>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: adding the commit to a patch's thread
Date: 2017-09-02 22:00:10
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 01 Sep 2017, at 15:40, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Sep 1, 2017 at 4:26 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>> Erik Rijkers wrote:
>>> Would it be possible to change the commitfest a bit and make it possible to
>>> add the commit (or commit-message, or hash) to the thread in the
>>> commitfest-app.
>> +1 to add one or more commit hashes to CF entry metadata.
>> (Back-filling for old entries welcome)
> Couldn't the CF app scrape the commit messages for references to
> threads, and if the commit message points to a thread with exactly 1
> patch record, associate the commit to that patch?

Since there is a Gitlink field in the patch metadata, we could start simple
with setting that to link to the commit on pg gitweb? While adding the thread
of the commit from -committers would be great as well, this gets us off the
ground quickly.

Unless there are objections, I’ll ensure that this is maintained during this CF
as part of my commitfest tinkering.

cheers ./daniel

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-09-02 22:20:28 Re: Function to move the position of a replication slot
Previous Message Tom Lane 2017-09-02 21:57:36 Re: [bug fix] Savepoint-related statements terminates connection