From: Kaushal Modi <kaushal.modi@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Debbugs email parser down?
Date: Wed, 20 Sep 2017 15:15:38 +0000 [thread overview]
Message-ID: <CAFyQvY2WE619tGr9+DiVNdMMWLbVM_TG47OvPmTKafsAfygtKA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
I sent a bug report to bug-gnu-emacs@gnu.org about hour and a half back.
But I still haven't received the automated confirmation and debbugs #
assignment for that.
Can someone check if that is working fine?
Thanks.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 461 bytes --]
next reply other threads:[~2017-09-20 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 15:15 Kaushal Modi [this message]
2017-09-20 15:16 ` Debbugs email parser down? Kaushal Modi
2017-09-20 21:28 ` Ian Kelling
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=CAFyQvY2WE619tGr9+DiVNdMMWLbVM_TG47OvPmTKafsAfygtKA@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-devel@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).