From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: commitfest app bug/feature |
Date: | 2015-05-08 00:30:14 |
Message-ID: | CAB7nPqQhyFQk1_2--jkakZySdAd3Q=iXB-PHqSUZotVyE5rAXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 8, 2015 at 4:17 AM, Fabien COELHO wrote:
> Then there is no way to remove a patch from the application. You end up
> marking them as "Rejected", which does not make much sense, see the bottom
> of the 2015-06 commitfest list...
> Maybe a "Duplicate" status would be better, and the ability to actually
> remove a stupid entry would be even nicer, although maybe not desirable, ot
> sure. And/or some way to prevent duplicates based on the description...
It is possible to remove patches from the set, but administrator
rights are necessary. If there are duplicated entries that you would
like to get removed, simply mention them here and I'll remove them. I
do some cleanup of duplicate entries from time to time though, you are
not the first one to get bitten by that.
Regards,
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2015-05-08 01:08:34 | Re: when are the xxxin() functions called |
Previous Message | Tom Lane | 2015-05-07 23:31:56 | Re: Fixing busted citext function declarations |