From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63831@debbugs.gnu.org, Amritpal Singh <icy.amrit@gmail.com>, rms@gnu.org
Subject: bug#63831: fix bug with failed inflation of .el.gz files in src/decompress.c
Date: Sun, 04 Jun 2023 08:30:18 +0200 [thread overview]
Message-ID: <87r0qrvix1.fsf_-_@gmx.de> (raw)
In-Reply-To: <83bkhv7pon.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Jun 2023 08:38:00 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi,
>> We've observed that me accidentally submitting a duplicate report
>> made it through human filters,
FTR, there are several moderators, so you cannot expect that both
reports have been seen by the same moderator (honestly, I don't
remember the case)
Furthermore, we don't decide on the contents. If something looks like a
valid bug report we approve, whatever it is about. No further checks on
duplicates or alike, that would exceed our limited resources.
>> I'm not trying to impugn someone else's ability of moderating but the current
>> system seems a little ineffective.
> I'm not sure I understand what you are suggesting here. What better
> system did you have in mind?
I don't feel offended :-)
Anyway, what we do is manual, human work. Do you recommend to hand over
moderation to ChatGPT? :-)
Best regards, Michael.
next prev parent reply other threads:[~2023-06-04 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 5:39 bug#63831: fix bug with failed inflation of .el.gz files in src/decompress.c Amritpal Singh
2023-06-02 8:05 ` bug#63831: Accidentally submit two bug reports for the same topic Amritpal Singh
2023-06-02 12:13 ` Eli Zaretskii
2023-06-03 21:27 ` Richard Stallman
2023-06-04 3:46 ` Amritpal Singh
2023-06-04 5:38 ` Eli Zaretskii
2023-06-04 5:47 ` Amritpal Singh
2023-06-04 6:30 ` Michael Albinus [this message]
2023-06-04 5:01 ` Eli Zaretskii
2023-06-04 6:13 ` Michael Albinus
2023-06-05 7:35 ` Richard Stallman
2023-06-05 8:17 ` Michael Albinus
2023-06-03 3:08 ` bug#63831: [PATCH] Elaboration on the bugfix for failed inflation of gz archives Amritpal Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0qrvix1.fsf_-_@gmx.de \
--to=michael.albinus@gmx.de \
--cc=63831@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=icy.amrit@gmail.com \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).