From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Can't build latest emacs on MSW + CRLF display issue
Date: Tue, 27 Aug 2013 14:54:17 -0400 [thread overview]
Message-ID: <4cli3nvuau.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83ob8jf9dy.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 27 Aug 2013 18:20:25 +0300")
Eli Zaretskii wrote:
>> On the other hand, I can't think of a single reason to _not_ remove it.
>
> The only reason is to let people have time to adapt to the change.
This only makes sense if the old method is still being updated and
supported, which it isn't. It is already incomplete.
Plus, there are pre-built binaries being supplied, so anyone who can't
adapt (for some reason) is already covered.
>> If someone turns up and wants to do 1), it will be the least of their
>> problems to first revert the commit that removed the old method.
>
> Not if they build out of the release (or release-like) tarball.
I hope we don't include an out-of-date, untested build process in the
next release. There are pre-built binaries of releases anyway, so again
I don't see the issue.
next prev parent reply other threads:[~2013-08-27 18:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 11:52 Can't build latest emacs on MSW + CRLF display issue Vincent Belaïche
2013-08-25 15:02 ` Eli Zaretskii
2013-08-25 19:00 ` Glenn Morris
2013-08-25 19:27 ` Eli Zaretskii
2013-08-25 19:40 ` Glenn Morris
2013-08-25 20:18 ` Vincent Belaïche
2013-08-25 20:36 ` Eli Zaretskii
2013-08-27 1:46 ` Glenn Morris
2013-08-27 15:20 ` Eli Zaretskii
2013-08-27 18:54 ` Glenn Morris [this message]
2013-08-27 19:11 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2013-08-25 18:54 Vincent Belaïche
2013-08-25 19:33 ` Eli Zaretskii
2013-08-26 6:06 Vincent Belaïche
2013-08-26 13:12 ` Eli Zaretskii
2013-08-27 2:28 Vincent Belaïche
2013-08-27 2:44 Vincent Belaïche
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=4cli3nvuau.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--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).