Re: CF app feature request - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: CF app feature request
Date
Msg-id CA+q6zcVoCy+Zi4PVKW=1kk2mdrn+wCkBFEm-HnqkcXoN1uHByA@mail.gmail.com
Whole thread Raw
In response to Re: CF app feature request  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: CF app feature request
List pgsql-hackers
On Fri, 2 Nov 2018 at 10:24, Fabien COELHO <coelho@cri.ensmp.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.


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: WIP Patch: Add a function that returns binary JSONB as a bytea
Next
From: Nikolay Shaplov
Date:
Subject: Re: [PATCH][PROPOSAL] Add enum releation option type