unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Amritpal Singh <icy.amrit@gmail.com>
To: rms@gnu.org
Cc: 63831@debbugs.gnu.org, "eliz@gnu.org" <eliz@gnu.org>
Subject: bug#63831: Accidentally submit two bug reports for the same topic
Date: Sun, 4 Jun 2023 09:16:49 +0530	[thread overview]
Message-ID: <CAAtEfCG+T2eC0UFMiUskdw8RAVkVDyArs0DwUzU_FXxuZpDGUA@mail.gmail.com> (raw)
In-Reply-To: <E1q5YmV-0005qw-B6@fencepost.gnu.org>

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]

>   > Please be more patient.  Each bug report is approved by a human, to
>   > avoid the catastrophic consequences of admitting spam to the bug list.
>   > So it might take some time, especially if the person who approves the
>   > bug reports and you live in different time zones.

> There are good reasons for this, but can we do something to help
> bug submitters understand the situation?

> For instance, we could set up an immeidate auto-reply to inform them
> of the delay to expect.

> If we had two people to do the moderation, maybe they could work
> at different times of day -- that would shorten the usual wait time
> without incresaing the work.

While we're on the topic of bug report moderation, is it possible that the
current human moderation might be a little ineffective? 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

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'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.

I wish you a good day/night and, again would like to apoligise for any
rude language.

Regards,
Amritpal Singh





  reply	other threads:[~2023-06-04  3:46 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 [this message]
2023-06-04  5:38         ` Eli Zaretskii
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=CAAtEfCG+T2eC0UFMiUskdw8RAVkVDyArs0DwUzU_FXxuZpDGUA@mail.gmail.com \
    --to=icy.amrit@gmail.com \
    --cc=63831@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).