From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Failure building Emacs master
Date: Tue, 21 Mar 2017 21:13:37 +0100 [thread overview]
Message-ID: <a318a810-d9b1-3a29-3d9a-aa44b9dc9fa5@alice.it> (raw)
In-Reply-To: <831stqwiu6.fsf@gnu.org>
Il 21/03/2017 20:06, Eli Zaretskii ha scritto:
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> Date: Tue, 21 Mar 2017 11:24:23 -0700
>> Cc: Emacs developers <emacs-devel@gnu.org>
>>
>> On 03/21/2017 09:45 AM, Angelo Graziosi wrote:
>>> It seems the patch is not yet applied on master..
>>
>> I applied it just now (with streamlined diagnostics), since you and I
>> liked the idea and there wasn't any opposing opinion.
>
> I reverted it, since I specifically asked not to make this the
> default.
>
..then you should fix also the configure warning... [*]
----
[*] http://lists.gnu.org/archive/html/emacs-devel/2017-03/msg00437.html
next prev parent reply other threads:[~2017-03-21 20:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:45 Failure building Emacs master Angelo Graziosi
2017-03-21 18:24 ` Paul Eggert
2017-03-21 19:06 ` Eli Zaretskii
2017-03-21 20:13 ` Angelo Graziosi [this message]
2017-03-21 20:59 ` Paul Eggert
2017-03-22 16:10 ` Eli Zaretskii
2017-03-22 17:48 ` Paul Eggert
2017-03-22 19:52 ` Eli Zaretskii
2017-03-22 18:59 ` Angelo Graziosi
2017-03-22 19:05 ` Paul Eggert
2017-03-22 20:22 ` Eli Zaretskii
2017-03-26 9:37 ` Angelo Graziosi
2017-03-26 14:20 ` Eli Zaretskii
2017-03-22 16:08 ` Eli Zaretskii
2017-03-22 19:57 ` Colin Baxter
2017-03-22 20:12 ` Eli Zaretskii
2017-03-22 20:27 ` Colin Baxter
-- strict thread matches above, loose matches on Subject: below --
2017-03-18 16:53 Angelo Graziosi
2017-03-17 23:03 Angelo Graziosi
2017-03-17 23:07 ` Angelo Graziosi
2017-03-18 5:05 ` Paul Eggert
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=a318a810-d9b1-3a29-3d9a-aa44b9dc9fa5@alice.it \
--to=angelo.graziosi@alice.it \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).