From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: lekktu@gmail.com, 15183@debbugs.gnu.org
Subject: bug#15183: 24.3.50; emacs_backtrace.txt
Date: Sun, 25 Aug 2013 20:49:37 +0300 [thread overview]
Message-ID: <83k3j9hd8u.fsf@gnu.org> (raw)
In-Reply-To: <521A3F68.50700@gmx.at>
> Date: Sun, 25 Aug 2013 19:31:20 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: Juanma Barranquero <lekktu@gmail.com>, 15183@debbugs.gnu.org
>
> the attached patch should fix it but I don't have any idea how to
> test it.
Why, by committing it, of course.
Thanks.
next prev parent reply other threads:[~2013-08-25 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 1:01 bug#15183: 24.3.50; emacs_backtrace.txt Drew Adams
2013-08-25 1:51 ` Juanma Barranquero
2013-08-25 14:36 ` martin rudalics
2013-08-25 16:28 ` Drew Adams
2013-08-25 17:31 ` martin rudalics
2013-08-25 17:49 ` Eli Zaretskii [this message]
2013-08-26 13:06 ` martin rudalics
2013-08-26 13:34 ` Eli Zaretskii
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=83k3j9hd8u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15183@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--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).