From: Dan Nicolaescu <dann@ics.uci.edu>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 22.2 release plans
Date: Thu, 06 Mar 2008 08:12:53 -0800 [thread overview]
Message-ID: <200803061612.m26GCrHw005466@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <47D01307.8090404@gnu.org> (Jason Rumney's message of "Thu, 06 Mar 2008 15:51:35 +0000")
Jason Rumney <jasonr@gnu.org> writes:
> Dan Nicolaescu wrote:
> > The problem with warnings is that using
> >
> > ./configure && make
> >
> > is quite common, so seeing the warning is almost impossible.
> >
>
> What about using a --force-obsolete option to configure to force it to
> continue past the warning, rather than requiring users to edit the
> configure script themselves?
Too disruptive for the configure script so close to the release.
And this is designed to force users take an action.
(BTW, Stefan originally wanted this to be #error in src/[ms]/*.h)
This is for stuff that is quite likely dead (things like HPUX running on
m68k). Why do people all of a sudden care about this???
next prev parent reply other threads:[~2008-03-06 16:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 19:53 Emacs 22.2 release plans Chong Yidong
2008-03-05 17:25 ` Chong Yidong
2008-03-05 23:58 ` Kim F. Storm
2008-03-06 0:38 ` Glenn Morris
2008-03-06 11:19 ` Kim F. Storm
2008-03-06 15:16 ` Dan Nicolaescu
2008-03-06 15:51 ` Jason Rumney
2008-03-06 16:12 ` Dan Nicolaescu [this message]
2008-03-06 17:32 ` Stefan Monnier
2008-03-06 17:31 ` Stefan Monnier
2008-03-06 18:56 ` Chong Yidong
2008-03-07 10:55 ` Kim F. Storm
2008-03-06 22:38 ` Emacs 22.2 release plans - request for a slight delay Alan Mackenzie
2008-03-06 23:19 ` Chong Yidong
2008-03-07 7:25 ` Alan Mackenzie
2008-03-07 16:17 ` Chong Yidong
2008-03-07 23:15 ` Alan Mackenzie
2008-03-07 23:04 ` Chong Yidong
2008-03-07 23:33 ` Nick Roberts
2008-03-07 23:24 ` Alan Mackenzie
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=200803061612.m26GCrHw005466@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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).