From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lewis Creary <lewcreary@cs.com>, 66474@debbugs.gnu.org
Subject: bug#66474: No response to my emacs bug report
Date: Thu, 12 Oct 2023 11:52:13 +0200 [thread overview]
Message-ID: <8734yggoc2.fsf@gmx.de> (raw)
In-Reply-To: <83zg0oto70.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Oct 2023 08:16:51 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Lewis,
>> Several days ago I reported bug in Gnu emacs using the M-x report-emacs-bug command, but have
>> received no response, contrary to the stated emacs policy of responding to such reports within a day
>> or so. Did you receive my report, or should I send it again?
>
> Please tell more about the bug you sent: its Subject, or the actual
> report, or some other information we could use to try to find your
> report in the bug database. I tried searching using your name, but
> couldn't find anything.
>
> Did you receive an automated response from the bug-tracker with a bug
> number? If not, maybe your report was classified as spam for some
> reason.
I've checked the mailman logs on debbugs.gnu.org. The only reference for
lewcreary@cs.com, your email address, is
--8<---------------cut here---------------start------------->8---
Oct 11 22:24:35 2023 (746) post to debbugs-submit from lewcreary@cs.com, size=7466, message-id=<1965688274.4309065.1697077337578@mail.yahoo.com>, success
--8<---------------cut here---------------end--------------->8---
This is the message which has arrived for *this* report,
bug#66474. However, the logs show only accepted messages. If a message
is discarded by a moderator, we won't see it in the logs, and you won't
receive an information about.
I recommend you re-submit your bug report. In parallel you might send me
a note containing the complete sent message, including all headers.
Best regards, Michael.
next prev parent reply other threads:[~2023-10-12 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1965688274.4309065.1697077337578.ref@mail.yahoo.com>
2023-10-12 2:22 ` bug#66474: No response to my emacs bug report Lewis Creary via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 5:16 ` Eli Zaretskii
2023-10-12 9:52 ` Michael Albinus [this message]
[not found] ` <1718218707.6284256.1697140654254@mail.yahoo.com>
[not found] ` <87pm1jwplo.fsf@gmx.de>
[not found] ` <1028396789.8098323.1697211479026@mail.yahoo.com>
2023-10-14 13:21 ` Michael Albinus
2024-01-10 18:07 ` Stefan Kangas
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=8734yggoc2.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=66474@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lewcreary@cs.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 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).