GNU bug report logs -
#66474
No response to my emacs bug report
Previous Next
Reported by: Lewis Creary <lewcreary <at> cs.com>
Date: Thu, 12 Oct 2023 02:25:01 UTC
Severity: normal
Done: Stefan Kangas <stefankangas <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 66474 in the body.
You can then email your comments to 66474 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66474
; Package
emacs
.
(Thu, 12 Oct 2023 02:25:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Lewis Creary <lewcreary <at> cs.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Thu, 12 Oct 2023 02:25:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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?
Yours truly,
Lewis Creary,,,,,,
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66474
; Package
emacs
.
(Thu, 12 Oct 2023 05:18:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 66474 <at> debbugs.gnu.org (full text, mbox):
> Cc: "lewcreary <at> cs.com" <lewcreary <at> cs.com>
> Date: Thu, 12 Oct 2023 02:22:17 +0000 (UTC)
> From: Lewis Creary via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>
> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66474
; Package
emacs
.
(Thu, 12 Oct 2023 09:53:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 66474 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> 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 <at> cs.com, your email address, is
--8<---------------cut here---------------start------------->8---
Oct 11 22:24:35 2023 (746) post to debbugs-submit from lewcreary <at> cs.com, size=7466, message-id=<1965688274.4309065.1697077337578 <at> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66474
; Package
emacs
.
(Sat, 14 Oct 2023 13:23:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 66474 <at> debbugs.gnu.org (full text, mbox):
Lewis Creary <lewcreary <at> cs.com> writes:
> Michael,
Hi Lew,
>>>> Hmm. I don't see the new message yet in the debbugs logs.
>
> I think I have now identified the information that will permit you to
> find my bug report in the "debbugs" logs. The info is my mangled
> email address, which I found in my file
> c:Users/lewcr/AppData/Roaming/message-20231009-125408 --
> lewcremaceary <at> cs.com. If you look in the logs for this address, I
> think you will find my report.
There is no hit for the string "lewcremaceary" in the debbugs mailman
logs. However, not all logs are based on email address. But all of them
trace the Message-ID. So for a better search I need the Message-ID of a
lost message.
> Thanks -- Lew
Best regards, Michael.
Reply sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
You have taken responsibility.
(Wed, 10 Jan 2024 18:08:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Lewis Creary <lewcreary <at> cs.com>
:
bug acknowledged by developer.
(Wed, 10 Jan 2024 18:08:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 66474-done <at> debbugs.gnu.org (full text, mbox):
Michael Albinus <michael.albinus <at> gmx.de> writes:
> Eli Zaretskii <eliz <at> 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 <at> cs.com, your email address, is
>
> Oct 11 22:24:35 2023 (746) post to debbugs-submit from lewcreary <at> cs.com, size=7466, message-id=<1965688274.4309065.1697077337578 <at> mail.yahoo.com>, success
>
> 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.
I hope that helped, in any case this is not a bug in Emacs itself so I'm
closing the bug report now.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 08 Feb 2024 12:24:16 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 92 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.