unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63831@debbugs.gnu.org, icy.amrit@gmail.com, rms@gnu.org
Subject: bug#63831: Accidentally submit two bug reports for the same topic
Date: Sun, 04 Jun 2023 08:13:32 +0200	[thread overview]
Message-ID: <871qirwy9f.fsf@gmx.de> (raw)
In-Reply-To: <83legz7re7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Jun 2023 08:01:04 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli & Richard,

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

No. This would send the information to spam factories that the given
email address on debbugs.gnu.org is valid. Meaning increasing the
amount of spam.

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

AFAIK, Bob Proulx and me are moderating. Bob lives in the USA
(Colorado?), I live in Germany, so there are different time zones.

Usually, I check debbugs for hold messages several times a day. A delay
of 1.5 hours, as reported here, is completely normal. We cannot change
it unless we could recruit more moderators.

Best regrds, Michael.





  reply	other threads:[~2023-06-04  6:13 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           ` 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 [this message]
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=871qirwy9f.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).