From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Failure building Emacs master
Date: Wed, 22 Mar 2017 22:22:02 +0200 [thread overview]
Message-ID: <83o9wt5afp.fsf@gnu.org> (raw)
In-Reply-To: <b8673ad9-bf09-dc4e-4601-91a63965e76b@alice.it> (message from Angelo Graziosi on Wed, 22 Mar 2017 19:59:51 +0100)
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> Date: Wed, 22 Mar 2017 19:59:51 +0100
> Cc: emacs-devel@gnu.org
>
> Really, I don't like the warning from 'configure' for a default feature.
It's a first step towards removing the feature in some future
release. How else would you suggest to warn users and distributions
about the issue without making drastic backward-incompatible changes
in the build products?
> In any case now the message seem clear enough and you can "close" this
> "issue"..
Sorry, I don't understand the quotes. If you are unhappy about the
solution, even after your questions were answered, let's try to find a
better one.
next prev parent reply other threads:[~2017-03-22 20:22 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o9wt5afp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=eggert@cs.ucla.edu \
--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 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.