From: Chong Yidong <cyd@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: "Jan Djärv" <jan.h.d@swipnet.se>, emacs-devel@gnu.org
Subject: Re: Trunk does not compile, undefined interval_* (a lot of them)
Date: Fri, 10 Aug 2012 21:32:14 +0800 [thread overview]
Message-ID: <871ujevpnl.fsf@gnu.org> (raw)
In-Reply-To: <50250BEB.2050003@yandex.ru> (Dmitry Antipov's message of "Fri, 10 Aug 2012 17:26:03 +0400")
Dmitry Antipov <dmantipov@yandex.ru> writes:
>> Compile without optimizations.
>
> OK, got it. Should be fixed in 109551.
In the first place, what problem is this patch trying to solve?
prev parent reply other threads:[~2012-08-10 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 12:40 Trunk does not compile, undefined interval_* (a lot of them) Jan Djärv
2012-08-10 12:52 ` Dmitry Antipov
2012-08-10 12:54 ` Jan Djärv
2012-08-10 13:16 ` Jan Djärv
2012-08-10 13:26 ` Dmitry Antipov
2012-08-10 13:32 ` Chong Yidong [this message]
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=871ujevpnl.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/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).