| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: commitfest app bug/feature |
| Date: | 2015-05-08 09:02:16 |
| Message-ID: | alpine.DEB.2.10.1505081056440.20788@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> ISTM that an additional "Duplicate" or "To remove" status could be a tag for
>> admins to remove the entries?
>
> This looks like an overkill to me. Entries with the same description
> headline mean the same thing.
Sure.
My point was to provide a mean to signal explicitely that an entry can be
removed, as removing it is not an option for the lay man, and all other
status do not correspond to reality (Why put Rejected or Returned with
feedback, as it is not the case in?). Morover the description if different
submitions might be slightly different.
ISTM that sending a mail to hacker to remove spurious entries in the CF
app is a little overkill too.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoff Winkless | 2015-05-08 09:06:53 | Re: INSERT ... ON CONFLICT syntax issues |
| Previous Message | Simon Riggs | 2015-05-08 06:55:13 | Re: subxcnt defined as signed integer in SnapshotData and SerializeSnapshotData |