all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org, vuori@notcom.org
Subject: Re: emacs-29 b54febef5d7: Fix NetBSD build with and without ncurses
Date: Sun, 16 Jul 2023 15:56:38 +0300	[thread overview]
Message-ID: <83v8ek816h.fsf@gnu.org> (raw)
In-Reply-To: <87edl883zr.fsf@yahoo.com> (message from Po Lu on Sun, 16 Jul 2023 19:55:52 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org,  vuori@notcom.org
> Date: Sun, 16 Jul 2023 19:55:52 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > We use -o in other places with 'test'.
> 
> Not in Emacs 28.

We are not releasing Emacs 28 anymore.

> configure.in only contains `test ... -o ...' in two places, both
> additions in Emacs 29, which will also affect user's ability to
> configure Emacs.  So I would really prefer to have this fixed in the
> release branch.
> 
> > So this is evidently not a problem.
> 
> Dozens of years of Autoconf developers' experience says otherwise.

Sorry, I'm not going to install unnecessary changes on emacs-29 at
this stage.  It's too late for that.  The change I installed was
tested on the only affected system, and any further changes mean more
delays and/or risk of introducing bugs.



  reply	other threads:[~2023-07-16 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168940883684.23439.12214259073355647832@vcs2.savannah.gnu.org>
     [not found] ` <20230715081357.2B622C06C71@vcs2.savannah.gnu.org>
2023-07-16 10:02   ` emacs-29 b54febef5d7: Fix NetBSD build with and without ncurses Po Lu
2023-07-16 10:31     ` Eli Zaretskii
2023-07-16 11:55       ` Po Lu
2023-07-16 12:56         ` Eli Zaretskii [this message]
2023-07-16 13:44           ` Po Lu

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=83v8ek816h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=vuori@notcom.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.