From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Can't build latest emacs on MSW + CRLF display issue
Date: Sun, 25 Aug 2013 23:36:12 +0300 [thread overview]
Message-ID: <83d2p1h5j7.fsf@gnu.org> (raw)
In-Reply-To: <xk4nadzhhf.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Date: Sun, 25 Aug 2013 15:40:44 -0400
> Cc: vincent.b.1@hotmail.fr, emacs-devel@gnu.org, karl@freefriends.org
>
> Eli Zaretskii wrote:
>
> >> If you don't want to remove this old method (I really don't get this,
> >> but we've been over this before), can it at least print a big fat
> >> warning when it starts, maybe even with a "press return to continue at
> >> your own risk" or somesuch. (Maybe it does this already.)
> >
> > Feel free to add that, I don't want to invest even a few seconds of my
> > time on this.
>
> I'd much rather remove it all together, but you won't allow it.
> Therefore we are stuck in this state.
With any other deprecated feature, we usually let it linger for quite
some time before deleting it. I have no idea why this particular case
should be different (nor, for that matter, why it triggers such strong
emotions).
next prev parent reply other threads:[~2013-08-25 20:36 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 [this message]
2013-08-27 1:46 ` Glenn Morris
2013-08-27 15:20 ` Eli Zaretskii
2013-08-27 18:54 ` Glenn Morris
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=83d2p1h5j7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).