unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Amritpal Singh <icy.amrit@gmail.com>
Cc: 63831@debbugs.gnu.org, rms@gnu.org
Subject: bug#63831: Accidentally submit two bug reports for the same topic
Date: Sun, 04 Jun 2023 08:38:00 +0300	[thread overview]
Message-ID: <83bkhv7pon.fsf@gnu.org> (raw)
In-Reply-To: <CAAtEfCG+T2eC0UFMiUskdw8RAVkVDyArs0DwUzU_FXxuZpDGUA@mail.gmail.com> (message from Amritpal Singh on Sun, 4 Jun 2023 09:16:49 +0530)

> From: Amritpal Singh <icy.amrit@gmail.com>
> Date: Sun, 4 Jun 2023 09:16:49 +0530
> Cc: "eliz@gnu.org" <eliz@gnu.org>, 63831@debbugs.gnu.org
> 
> While we're on the topic of bug report moderation, is it possible that the
> current human moderation might be a little ineffective?

Feel free to volunteer to help, in order to improve the quality and
the timeliness of the moderation.

> We've observed that me accidentally submitting a duplicate report
> made it through human filters, and I had notice another instance of
> a "spam" email, where no subject or body was present.  See:
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2023-06/msg00107.html

It isn't spam.  The sender is an Emacs contributor.

> I'm not trying to impugn someone else's ability of moderating but the current
> system seems a little ineffective. Also I'd like to apologize if my
> language/wording
> seems abrasive towards the moderation team as this is no way an insult to their
> work but rather a lack of implementation of better systems by management.

I'm not sure I understand what you are suggesting here.  What better
system did you have in mind?

(In any case, discussing this as part of a specific bug report is
wrong; this should be taken to emacs-devel instead.)

> I'd also like to draw attention towards the actual bug+patch report
> #63831, it's been
> close to two days now and such a small change could easily be merged into HEAD.
> But the bug does seem low priority (even though breaking) to me as well so
> I would not question the maintainers' decision to prioritize critical
> bugs over this.

That bug is indeed low priority, and the change will go to master,
which makes it even lower priority (since we are in the process of
pretesting Emacs 29.1).  The bug report is in my queue, and two days
is really way too short to ring the alarm bells about such a minor
issue.





  reply	other threads:[~2023-06-04  5:38 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 [this message]
2023-06-04  5:47           ` Amritpal Singh
2023-06-04  6:30           ` bug#63831: fix bug with failed inflation of .el.gz files in src/decompress.c Michael Albinus
2023-06-04  5:01       ` bug#63831: Accidentally submit two bug reports for the same topic 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=83bkhv7pon.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63831@debbugs.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).