From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Bug tracker automated control server message
Date: Sat, 31 Aug 2013 14:39:34 +0300 [thread overview]
Message-ID: <83fvtqdr7t.fsf@gnu.org> (raw)
In-Reply-To: <5221AB9F.7090209@gmx.at>
> Date: Sat, 31 Aug 2013 10:38:55 +0200
> From: martin rudalics <rudalics@gmx.at>
>
> The "GNU bug tracker automated control server" just told me that
>
> > Processing commands for control@debbugs.gnu.org:
> >
> >> >> w32_backtrace at w32fns.c:7982
> > Unknown command or malformed arguments to command.
> >
> >> >> emacs_abort at w32fns.c:8014
> > Unknown command or malformed arguments to command.
> >
> >> >> terminate_due_to_signal at emacs.c:369
> > Unknown command or malformed arguments to command.
> >
> >> >> die at alloc.c:6573
> > Unknown command or malformed arguments to command.
> >
> >> >> XWINDOW at lisp.h:799
> > Unknown command or malformed arguments to command.
> >
> > Too many unknown commands, stopping here.
> >
> > No commands successfully parsed; sending the help text(s).
> > Sending instructions for control@debbugs.gnu.org in separate message.
> >
> > Please contact help-debbugs@gnu.org if you need assistance.
> >
> > GNU bugs database, http://debbugs.gnu.org/
>
> I'd like to avoid this. Any suggestions?
Put "stop" or "thanks" line before the stuff that isn't meant for the
tracker.
next prev parent reply other threads:[~2013-08-31 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5221A64B.5000207@gmx.at>
[not found] ` <handler.s.C.137793698428616.transcript@debbugs.gnu.org>
2013-08-31 8:38 ` Bug tracker automated control server message martin rudalics
2013-08-31 11:39 ` Eli Zaretskii [this message]
2013-08-31 12:56 ` martin rudalics
2013-08-31 13:04 ` David Engster
2013-08-31 13:07 ` martin rudalics
2013-08-31 13:45 ` Eli Zaretskii
2013-08-31 16:06 ` David Engster
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=83fvtqdr7t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).