From: Amritpal Singh <icy.amrit@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63831@debbugs.gnu.org
Subject: bug#63831: Accidentally submit two bug reports for the same topic
Date: Sun, 4 Jun 2023 11:17:52 +0530 [thread overview]
Message-ID: <CAAtEfCHHR5_d0QUBuQStzoTi4znbiDVsW++vW0daRVZ_7fPABA@mail.gmail.com> (raw)
In-Reply-To: <83bkhv7pon.fsf@gnu.org>
> Feel free to volunteer to help, in order to improve the quality and
> the timeliness of the moderation.
Thank you! Please let me know how I can contribute to this.
> It isn't spam. The sender is an Emacs contributor.
Apologies, I'm new to emacs mailing lists and unfamiliar with the
contributors, and I considered the empty email spam.
> 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.)
Like RMS suggested, perhaps an automated immediate response
system for reports would indeed be a good choice to indicate to
contributors that their report indeed has been received.
I agree with the latter part about moving to emacs-devel.
> 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.
I'm sorry for that as well, like I mentioned before I'm a newbie contributor and
do not have the know-how with how contributors and maintainers interact.
This is no excuse for being impatient but I thought I'd explain myself.
Thank you!
next prev parent reply other threads:[~2023-06-04 5:47 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 [this message]
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=CAAtEfCHHR5_d0QUBuQStzoTi4znbiDVsW++vW0daRVZ_7fPABA@mail.gmail.com \
--to=icy.amrit@gmail.com \
--cc=63831@debbugs.gnu.org \
--cc=eliz@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).