From: Paul Eggert <eggert@cs.ucla.edu>
To: Philipp Stephani <p.stephani2@gmail.com>, emacs-devel@gnu.org
Subject: Re: Undefined behavior in OS X unexec detected by ASan
Date: Sun, 15 May 2016 12:54:23 -0700 [thread overview]
Message-ID: <5738D3EF.2050502@cs.ucla.edu> (raw)
In-Reply-To: <CAArVCkQzjW6twYCBZ_rWWFsHaXY2qdaREJn-p6SMnj+QZcxxnQ@mail.gmail.com>
Philipp Stephani wrote:
> Friendly ping?
That patch was committed to the emacs-25 branch and merged to master on April 9.
next prev parent reply other threads:[~2016-05-15 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 17:26 Undefined behavior in OS X unexec detected by ASan Philipp Stephani
2016-04-08 8:27 ` Eli Zaretskii
2016-04-08 16:01 ` John Wiegley
2016-05-15 19:36 ` Philipp Stephani
2016-05-15 19:54 ` Paul Eggert [this message]
2016-05-15 19:58 ` Philipp Stephani
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=5738D3EF.2050502@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
/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).