From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: commit fest app: Authors |
Date: | 2019-01-05 01:15:27 |
Message-ID: | 20190105011527.GC4849@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 04, 2019 at 10:05:25AM -0500, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Fri, Jan 4, 2019 at 12:26 PM Peter Eisentraut <
>> peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>>> Why does the commit fest app not automatically fill in the author for a
>>> new patch?
>
>> I'm not sure it's a good idea to *enforce* it -- because you can't register
>> an author until they have logged into the CF app once. And I think
>> registering it with no author is better than registering it with the wrong
>> author.
>
> Yeah --- I've not checked in detail, but I supposed that most/all of the
> cases of that correspond to authors with no community account to connect
> the patch to.
Agreed. It is worse to not track a patch than to track it without an
author, whom can be guessed from the thread attached to a patch
anyway...
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-01-05 01:19:41 | Re: A few new options for vacuumdb |
Previous Message | Michael Paquier | 2019-01-05 01:12:30 | Re: [PATCH] Log PostgreSQL version number on startup |