From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13788@debbugs.gnu.org
Subject: bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations
Date: Sat, 23 Feb 2013 14:19:04 +0100 [thread overview]
Message-ID: <5128C1C8.4050507@easy-emacs.de> (raw)
In-Reply-To: <83d2vrl3zb.fsf@gnu.org>
Am 23.02.2013 11:27, schrieb Eli Zaretskii:
>> Date: Sat, 23 Feb 2013 08:32:27 +0100
>> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
>> CC: 13788@debbugs.gnu.org
>>
>> Well, the point is: present implementation clutters reports with directives useless for the receiver.
>
> They are not useless for me, when I'm the receiver.
>
So let's consider a typical beginning of a bug report when sent not by a core developer,
let's take bug#13787. It starts:
This bug report will be sent to the Bug-GNU-Emacs mailing list
and the GNU bug tracker at debbugs.gnu.org. Please check that
the From: line contains a valid email address. After a delay of up
to one day, you should receive an acknowledgement at that address.
Please write in English if possible, as the Emacs maintainers
usually do not have translators for other languages.
Please describe exactly what actions triggered the bug, and
the precise symptoms of the bug. If you can, give a recipe
starting from `emacs -Q':
;;;;;;;
You really mean that kind of info is useful for you?
next prev parent reply other threads:[~2013-02-23 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 18:21 bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations Andreas Röhler
2013-02-22 18:24 ` Glenn Morris
2013-02-22 20:04 ` Eli Zaretskii
2013-02-22 21:27 ` Andreas Röhler
2013-02-22 21:46 ` Eli Zaretskii
2013-02-23 7:32 ` Andreas Röhler
2013-02-23 10:27 ` Eli Zaretskii
2013-02-23 13:19 ` Andreas Röhler [this message]
2013-02-23 14:51 ` Eli Zaretskii
2013-02-23 16:44 ` Andreas Röhler
2013-02-23 17:01 ` Stefan Monnier
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=5128C1C8.4050507@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=13788@debbugs.gnu.org \
--cc=eliz@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).