From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org, angelo.graziosi@alice.it
Subject: Re: Failure building Emacs master
Date: Wed, 22 Mar 2017 18:10:03 +0200 [thread overview]
Message-ID: <83y3vx5m3o.fsf@gnu.org> (raw)
In-Reply-To: <dd39d481-660f-b16a-16a9-222e07a5285e@cs.ucla.edu> (message from Paul Eggert on Tue, 21 Mar 2017 13:59:08 -0700)
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 21 Mar 2017 13:59:08 -0700
>
> In <http://bugs.gnu.org/26102#39> you asked not to remove the POP source
> code.
Not the POP source code, the fact that we build and install movemail
by default.
> I installed the attached patch to try to improve the 'configure'
> diagnostics. Please feel free to revert or improve it if you think the
> patch makes this confusing area even more confusing.
Thanks. The message is fine with me, but I think Angelo should tell
if it's clear enough now.
next prev parent reply other threads:[~2017-03-22 16:10 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 [this message]
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=83y3vx5m3o.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 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).