From: Eli Zaretskii <eliz@gnu.org>
To: Amritpal Singh <icy.amrit@gmail.com>
Cc: 63831@debbugs.gnu.org
Subject: bug#63831: Accidentally submit two bug reports for the same topic
Date: Fri, 02 Jun 2023 15:13:39 +0300 [thread overview]
Message-ID: <83bkhyawp8.fsf@gnu.org> (raw)
In-Reply-To: <CAAtEfCGCwCo7QFWukT+5604-5Ao4sLYYq=J-WgNY28LVuF+38w@mail.gmail.com> (message from Amritpal Singh on Fri, 2 Jun 2023 13:35:38 +0530)
> From: Amritpal Singh <icy.amrit@gmail.com>
> Date: Fri, 2 Jun 2023 13:35:38 +0530
>
> I'd like to apologise for submitting two bug reports, as I'd sent
> another after ~1.5 hour of submitting this bug report. I hadn't
> received any acknowledgement from the automatic bug tracking system
> and thought I'd submitted the report in a wrong method.
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.
next prev parent reply other threads:[~2023-06-02 12: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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkhyawp8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63831@debbugs.gnu.org \
--cc=icy.amrit@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.