| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CF app feature request |
| Date: | 2018-11-02 20:15:36 |
| Message-ID: | CA+q6zcVoCy+Zi4PVKW=1kk2mdrn+wCkBFEm-HnqkcXoN1uHByA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2 Nov 2018 at 10:24, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>
>
> Bonjour Michaël,
>
> >> Because the same patch submission is already counted? It is a rare
> >> occurence, so just a "Withdrawn" state could be enough, and slightly false
> >> CF stats are no big deal.
> >
> > Or as we are dealing with duplicated entries, perhaps we could just
> > delete the entry not wanted, which seems to be 1859 in this case.
> > Admins can do so.
>
> Good. Please proceed!
>
> So the solution is to contact an admin (no clear cue about who is an
> admin, though) to remove the entry.
Just to make sure, if a duplicated entry will be removed, the patch itself
will stay or not? I'm asking, because both entries have the same patch
referenced, and the admin form says that one of the related items, that
would be removed is the patch item.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Shaplov | 2018-11-02 20:52:13 | Re: [PATCH][PROPOSAL] Add enum releation option type |
| Previous Message | Merlin Moncure | 2018-11-02 20:05:41 | Re: WIP Patch: Add a function that returns binary JSONB as a bytea |