Re: CF app feature request
| От | Magnus Hagander |
|---|---|
| Тема | Re: CF app feature request |
| Дата | |
| Msg-id | CABUevEyjc5rDMBZU0nWHw2NxvLW_ZJ3e9owQLuF+9qGAujOAMA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: CF app feature request (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: CF app feature request
|
| Список | pgsql-hackers |
On Sun, Nov 4, 2018 at 1:28 AM Michael Paquier <michael@paquier.xyz> wrote:
On Fri, Nov 02, 2018 at 09:15:36PM +0100, Dmitry Dolgov wrote:
> 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.
If you remove only one entry, its references will be removed but the
second one will remain. If you want me to proceed, I can do so. I have
done that in the past, and it is not the first time someone registers a
duplicated entry in the CF app.
I'm trying to figure out where this thread left off :) My understanding of the consensus is we don't actually want/need a change in the app, but are instead OK with the admin just handling it a somewhat ugly way in the few cases where it's necessary?
Or is the consensus to add a "Withdrawn" status, just to solve a slightly different problem from the one that started this thread?
В списке pgsql-hackers по дате отправления: