all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Lewis Creary <lewcreary@cs.com>
Cc: 66474@debbugs.gnu.org
Subject: bug#66474: No response to my emacs bug report
Date: Sat, 14 Oct 2023 15:21:26 +0200	[thread overview]
Message-ID: <87wmvpnxux.fsf@gmx.de> (raw)
In-Reply-To: <1028396789.8098323.1697211479026@mail.yahoo.com> (Lewis Creary's message of "Fri, 13 Oct 2023 15:37:59 +0000 (UTC)")

Lewis Creary <lewcreary@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@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.





  parent reply	other threads:[~2023-10-14 13:21 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
     [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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wmvpnxux.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=66474@debbugs.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 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.