all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 13788@debbugs.gnu.org
Subject: bug#13788: 24.3.50; report-emacs-bug; report-emacs-bug-no-explanations
Date: Sat, 23 Feb 2013 16:51:36 +0200	[thread overview]
Message-ID: <838v6fkrrb.fsf@gnu.org> (raw)
In-Reply-To: <5128C1C8.4050507@easy-emacs.de>

> Date: Sat, 23 Feb 2013 14:19:04 +0100
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> CC: 13788@debbugs.gnu.org
> 
> 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?

Yes.  It tells me that the person who reports the bug didn't censor
her report in any way.






  reply	other threads:[~2013-02-23 14:51 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
2013-02-23 14:51             ` Eli Zaretskii [this message]
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

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

  git send-email \
    --in-reply-to=838v6fkrrb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13788@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    /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.